Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Share Post: Reddit Facebook
Reducing Chrome crashes caused by third-party software
#1
https://blog.chromium.org/2017/11/reduci...third.html       Reducing Chrome crashes caused by third-party software
Thursday, November 30, 2017
Roughly two-thirds of Windows Chrome users have other applications on their machines that interact with Chrome, such as accessibility or antivirus software. In the past, this software needed to inject code in Chrome in order to function properly; unfortunately, users with software that injects code into Windows Chrome are 15% more likely to experience crashes. With Chrome extensions and Native Messaging, there are now modern alternatives to running code inside of Chrome processes. Starting in July 2018, Chrome 68 will begin blocking third-party software from injecting code into Chrome on Windows.
These changes will take place in three phases. In April 2018, Chrome 66 will begin showing affected users a warning after a crash, alerting them that other software is injecting code into Chrome and guiding them to update or remove that software.

In Chrome 66 a warning will be shown to users with third-party software that injects into Chrome.
In July 2018, Chrome 68 will begin blocking third-party software from injecting into Chrome processes. If this blocking prevents Chrome from starting, Chrome will restart and allow the injection, but also show a warning that guides the user to remove the software. Finally, in January 2019, Chrome 72 will remove this accomodation and always block code injection.
While most software that injects code into Chrome will be affected by these changes, there are some exceptions. Microsoft-signed code, accessibility software, and IME software will not be affected. As with all Chrome changes, developers are encouraged to use Chrome Beta for early testing.
Fewer crashes means more happy users, and we look forward to continuing to make Chrome better for everyone.
Posted by Chris Hamilton, Chrome Stability Team
Reply
#2
I think that hitmanpro.alert injects codes to protect the browser against keylogger, also the antivirus too injects code into navigator (such as eset's online banking) (the protection of WEBROOT identityshield, password manager and filtering extension), likewise, internet download manager will be affected, It's an point into favor, to avoid injections and to have totally clean, isolated our browser with the OS. but very bad for those of us who its using extensions that are not in the chromestore.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Acrobat DC crashes intermittently on Windows tarekma7 0 2,755 05-28-2017 , 09:42 PM
Last Post: tarekma7

Forum Jump:


Users browsing this thread: 1 Guest(s)