javascript Chrome“无响应页面”误报（自 Chrome 32 起）

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

提问by Steven Lu

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:

自从 Chrome 将自己更新到版本 32 以来，我一直在遇到越来越严重的错误。最糟糕的情况之一是在使用 Web Inspector 编辑 DOM 时，Chrome 大约每分钟都会开始弹出此对话框，这会从 Web Inspector 中拉出焦点：

It's complaining about the Web Inspector itself being "unresponsive", when it really isn't, and nothing's gone wrong.

它抱怨 Web Inspector 本身“无响应”，而实际上并非如此，并且没有任何问题。

This particular page I'm messing with is making use of the mutation-summarylibrary. 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).

我正在处理的这个特定页面正在使用突变摘要库。也许 Chrome 中认为东西无响应的错误可能与设置各种连续运行的 setTimeouts 有关。我这样说是因为我在我们在工作中构建的网络应用程序中观察到类似的行为，这也开始发生（并且同样令人讨厌）。

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?

解决方法是我相信可以忽略对话框并继续工作。我想知道是否有其他人（或其他所有人）遇到过这个问题？

采纳答案by Xantix

I started getting this problem as well.

我也开始遇到这个问题。

In searching, I came accross this issue https://code.google.com/p/chromium/issues/detail?id=335248.

在搜索中，我遇到了这个问题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)

• 带有 Aero 主题的 Windows 7/8
• 页面上的滚动条（例如在开发者控制台中）
• 带有弹出窗口的页面（特别是 Window.open() 调用）

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

我猜他们打算将修复程序推送到版本 33 中……并且可能会保留稳定版* 32 的现状（尽管我希望不会）。

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.

• 退出 Aero Theme 直到版本 33 稳定
• 升级到 beta 频道，即版本 33
• 每当 chrome 开发人员工具打开时，每 30 秒单击一次“等待”按钮。

---

---

Update:

更新：

Chrome has released a hotfix into the version 32 stable channel. http://googlechromereleases.blogspot.ro/2014/01/stable-channel-update_27.html

Chrome 已在 32 版稳定频道中发布了一个修补程序。http://googlechromereleases.blogspot.ro/2014/01/stable-channel-update_27.html

Thanks to @probackpacker for bringing it to my attention.

感谢@probackpacker 引起我的注意。

回答by Martyn0627

I have also experienced this issue. The change of theme workaround has worked, and the Chromium team has provided the following update today:

我也遇到过这个问题。主题变通方法的更改已经奏效，Chromium 团队今天提供了以下更新：

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

...我们理解您的沮丧，并正在积极努力解决它。当您添加该评论时，会混淆关于我们是否能够在 Canary 上完全修复它的评论。如果我们能在canary中确认它已经完全修复，我们就可以合并到稳定通道中，每个人都可以得到修复。所以请不要说你也有这个问题。我向您保证，我们正在积极致力于修复。

This statement was taken from Chromium ticket #335248.

此语句取自Chromium 票证 #335248。

回答by Sameer Alibhai

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

好的，这是您无需更改主题即可执行的解决方案，右键单击我的计算机，转到系统属性，然后转到“高级”，单击“性能”下的“设置”，然后选中下面的单选按钮。这似乎阻止了它

回答by Sameer Alibhai

If the aero fix isn't working for you, download Chrome Beta

如果 aero fix 对您不起作用，请下载Chrome Beta

回答by CodingWithSpike

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.

我在 Chrome 32 上遇到了同样的问题（开发工具中有很多问题......）但是只有当我将开发工具从主浏览器窗口分离/取消停靠时才会发生这种情况。如果您在非停靠模式下使用它们，您可以通过重新停靠 devtools 来避免它。

回答by user3208387

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.

我在 Windows 上也遇到过这种情况，似乎在使用浏览器时通常会发生这种情况（不仅在 Web 检查器中）。在加载 Flash 内容（例如游戏）时，这种情况似乎也更频繁地发生。浏览器和flash 区域都正常响应，但浏览器认为它们没有任何原因。按等待似乎会将对话框隐藏几分钟，直到它再次重新出现。

I've read that this bug is fixed in the next beta (version 33).

我已经读到这个错误在下一个测试版（版本 33）中得到修复。

Regards, Moses

问候， 摩西

回答by Akash

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

您可以通过以下简单步骤在 Chrome 中解决此问题 - 1-转到设置 2-转到高级设置 3-取消选中“可用时使用硬件加速”。

回答by user2129697

August 6, 2014 - I solved this by installing the latest Chrome Beta https://www.google.com/chrome/browser/beta.html

2014 年 8 月 6 日 - 我通过安装最新的 Chrome Beta https://www.google.com/chrome/browser/beta.html解决了这个问题

回答by not sure...

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

我通过将调制解调器直接连接到我的 PC 解决了这个问题，没有重新安装或更改 Chrome 或任何东西。我跳过了通过无线路由器的连接，我认为这从一开始就是问题...现在 Chrome 无法加载的所有页面都可以正常加载。也许是时候换个新路由器了...