Chrome itself appears to work fine but I'm having problems with Developers Tools. After a short period of time it becomes unresponsive and the following dialog pops up...
Is this a known bug, can or will it be fixed soon? Also, the meantime what should I do, how can I roll back to older working version of Chrome?
I use Chrome and Developer Tools extensively and this is causing a major headache, so any advise would be welcome.
It is a known bug that got pushed with v32. I have not seen anything about fixing it yet though.
It happens with any model window (which includes devtools) or when Chrome is running in app mode.
Chrome isn't actually crashing and you can still continue to use it, but that will continually pop up with devtools open.
The issue has been fixed as of today's (1/28/2014) update. Version: 32.0.1700.102 m
I started getting this problem as well.
In searching, I came across this issue: "Page(s) Unresponsive" error messages in 32+.
As best I figured out, the bug is related to:
- Windows 7/8 with Aero Theme
- Scrollbars on pages (such as in the developer console)
- Pages with popups (in particular Window.open() calls)
I guess they are slated to push the fix into version 33...and maybe leave the stable* 32 how it is (I hope not).
So there are a few options:
- Switch away from Aero Theme until version 33 is in stable
- Upgrade to the beta channel, i.e. version 33
- Click on the Wait button every 30 seconds whenever the chrome developer tools is open (Don't try this at home).
Update:
The issue is resolved in Chrome Canary 34.0.1799.0. Read more:
@elewinso, Alternate place to look for the same registry key to disable Chrome autoupdate is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update..
Also, is there a way I can get notified when the next update happens? or, when can I remove this key?
upgrade chrome to Version 32.0.1700.102 m this fixes the problem
来源：https://stackoverflow.com/questions/21184844/chrome-developer-tools-unresponsive-since-update-32-0-1700-76-m