Chromium Blog
News and developments from the open source browser project
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 September 2018, Chrome 69 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 September 2018, Chrome 69 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 accommodation 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
Updated 2018-06-21: Third-party software will be blocked from injecting code into Chrome on Windows starting in Chrome 69.
Labels
$200K
1
10th birthday
4
abusive ads
1
accessibility
1
ad blocking
1
android
1
benchmarks
1
beta
14
billing
1
birthday
4
blink
1
browser
2
browser interoperability
1
capabilities
3
capable web
1
cds18
2
cds2018
1
chrome
11
chrome ads
1
chrome apps
3
chrome dev summit 2018
1
Chrome Frame
1
chrome web store
27
chromedevtools
1
chromeframe
3
chromeos
3
chromium
3
cloud print
1
coalition
1
coalition for better ads
1
dart
8
dashboard
1
day 2
1
design
1
devtools
12
discoverability
1
extensions
24
features
1
feedback
2
field data
1
frameworks
1
fund
1
funding
1
gdd
1
googlechrome
12
harmful ads
1
html5
11
incognito
1
javascript
3
lab data
1
lighthouse
1
linux
2
mac
1
mobile
2
na
1
native client
8
New Features
5
octane
1
open web
3
pagespeedinsights
1
performance
2
performance tools
1
play store
1
portals
1
progressive web apps
1
protection
1
pwa
1
releases
3
rlz
1
security
30
spdy
2
speed
1
ssl
2
store listing
1
subscription pages
1
tools
1
trusted web activities
1
twa
1
v8
6
web apps
1
web intents
1
web packaging
1
web.dev
1
webapi
1
webaudio
3
webgl
7
webkit
5
webmaster
1
webp
5
webrtc
4
websockets
5
webtiming
1
writable-files
1
Archive
2019
Feb
Jan
2018
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2017
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2016
Dec
Nov
Oct
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Feed
Google
on
Follow @ChromiumDev
Give us feedback in our
Product Forums
.
