Chrome "Unresponsive Page" false-positive (since Chrome 32)

Question

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?

Answer 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.

Answer 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