After leading a crusade against poor quality ads, auto-playing content with sound and unwanted redirects on Chrome, Google announced a smaller but still important initiative: reducing Chrome crashes caused by third-party software on Windows.
Chris Hamilton, of the Chrome Stability team, explained in a post that “About two-thirds of Windows Chrome users have other apps on their machines that interact with Chrome, such as accessibility or antivirus software. In the past, this software had to inject code into Chrome to work properly. Unfortunately, software users who inject code into Windows Chrome are 15% more likely to have crashes. With Chrome and Native Messaging extensions, there are now modern alternatives to code execution in Chrome processes. Beginning in July 2018, Chrome 68 will begin blocking code injections into Chrome on Windows by third-party software. ”
These changes will take place in three phases:
- In April 2018, Chrome 66 will begin notifying users after a crash, informing them that other software is injecting code into Chrome and guiding them to update or remove this software.
- in july 2018, Chrome 68 will start blocking the injection of third-party software into Chrome processes. If this blockage prevents Chrome from starting, Chrome will restart and allow the injection, but will also display a warning that guides the user to remove the software;
- finally, in January 2019, Chrome 72 will remove this step and will always block the injection of code.
“Although most software that feeds code into Chrome is affected by these changes, there are some exceptions. Codes signed by Microsoft, accessibility software and IME software will not be affected. As with all Chrome changes, developers are encouraged to use the beta version of Chrome for testing, “said Hamilton.