问题
Ever since Chrome updated itself to version 32, I have been experiencing aggravating bugs. One of the worst is when editing the DOM using the Web Inspector, and Chrome will about every minute start popping up this dialog, which yanks focus from the Web Inspector:
It's complaining about the Web Inspector itself being "unresponsive", when it really isn't, and nothing's gone wrong.
This particular page I'm messing with is making use of the mutation-summary library. Perhaps the bug in Chrome that thinks stuff is unresponsive could be related to setting various continuously-running setTimeouts. I say this because I observe similar behavior in the web app we build at work where this has also started happening (and is equally annoying).
The workaround is I believe it is possible to just ignore the dialog and work can continue. I wonder if anyone else (or everyone else) has been experiencing this issue?
回答1:
I started getting this problem as well.
In searching, I came accross this issue https://code.google.com/p/chromium/issues/detail?id=335248.
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 (although 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.
Update:
Chrome has released a hotfix into the version 32 stable channel. http://googlechromereleases.blogspot.ro/2014/01/stable-channel-update_27.html
Thanks to @probackpacker for bringing it to my attention.
回答2:
I have experienced this as well on Windows, it seems that this will happen in general when using the browser (not only within the web inspector). It also seems to happen more often when loading flash content (such as a game). The browser and flash areas are responding normally, but the browser thinks that they are not for whatever reason. Pressing wait seems to hide the dialog for a few minutes until it will re-appear again.
I've read that this bug is fixed in the next beta (version 33).
Regards, Moses
回答3:
I have also experienced this issue. The change of theme workaround has worked, and the Chromium team has provided the following update today:
... We understand your frustration and are actively working to resolve it. When you add that comment, it’s confusing the comments around whether we’re able to fully fix it on canary. If we can confirm it’s fully fixed in canary, we can merge into the stable channel and everyone can get the fix. So please refrain from saying thatyou’re having this problem, too. I assure you we’re actively working on a fix.
This statement was taken from Chromium ticket #335248.
回答4:
Okay here’s the solution you can do without changing your theme, right click on my computer, go to your System Properties, and then go to "Advanced", click on "Settings" under Performance, then check the below radio button. This seems to stop it
回答5:
If the aero fix isn't working for you, download Chrome Beta
回答6:
I have had this same issue with Chrome 32 (there are so many problems in the dev tools...) but it ONLY happens for me when I have the dev tools detached / undocked from the main browser window. You might be able to avoid it by re-docking the devtools if you are using them in un-docked mode.
回答7:
August 6, 2014 - I solved this by installing the latest Chrome Beta https://www.google.com/chrome/browser/beta.html
回答8:
You can solve this problem in Chrome by following simple steps- 1-Go to Setting 2-Go to Advance Setting 3-Uncheck the "Use Hardware Acceleration when available".
回答9:
I fixed that problem by linking modem directly to my PC, didn't reinstall or change Chrome or anything. I skipped connection through my wireless router which I think was the problem from the start... now all the pages Chrome couldn't load are loading with no problem at all. Maybe it's time to by a new router...
来源：https://stackoverflow.com/questions/21196189/chrome-unresponsive-page-false-positive-since-chrome-32