When running any version of Windows, chances are you are also running a program. This can be anything from accessibility to antivirus software, which can normally have the ability to inject code into your Google Chrome web browser. This is one of the reasons why Chrome keeps crashing Windows 10.
Google, the makers of Chrome, have had just about enough. While code injection has been a problem for a long time, the company has only just announced a solution for it. They have said that beginning July 2018, the web browser, or its updated version at least, will be blocking third-party software from inserting code into it. The version that will start doing this is Chrome 68. The current latest version of Chrome is 64.0.3282.186.
Google says that users with code injecting software (around two-thirds of Chrome users) on their PCs have 15 percent more chance of having their Chrome browser crash. The company will be using the block to force developers to come out with Chrome extensions and use Native Messaging instead of dubious software. The good side of this is that it ensures fewer crashes. The bad side is that browser-program integration will suffer.
There will be three steps to the change mentioned above. The first will be in April 2018, where Chrome 66 will start showing warnings to users after a crash. This will be to alert users that a program is trying to insert code into the browser. After this, the message will ask them to either perform an update or remove the problematic program.
After that, in July 2018, Chrome 68 will prevent third party software from injecting code into Chrome processes. If doing this stands in the way of the browser launching, then it will restart, and this time, allow the injection. Meanwhile, a warning will also be shown, saying that the user needs to get rid of the offending software. This many mean that either the program will have to be closed, or failing that, uninstalled from the system.
In January 2019, Chrome 72 will come out, and this version will always just block any injection of code. No questions will be asked, nor warnings shown.
There are some exceptions to this, however. Some code from companies like Microsoft will not be affected, and neither will accessibility software, or Input Method Editor (IME). Despite this, it is best that developers move forward and adopt Chrome extension programming and Native Messaging.