本文介绍了Chrome浏览器“无响应页面”假阳性(自Chrome 32以来)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧! 问题描述 29岁程序员,3月因学历无情被辞! 自从Chrome升级到32版以来,我一直在遇到令人烦恼的bug。其中最糟糕的是使用Web Inspector编辑DOM时,Chrome将每分钟开始弹出此对话框,该对话框将焦点集中在Web Inspector上: 这是抱怨Web Inspector本身就是没有反应,但实际上并没有什么问题。 我搞乱的这个特定页面是利用突变总结库。也许Chrome认为没有反应的错误可能与设置各种连续运行的setTimeout有关。我这样说是因为我观察到我们在工作中创建的web应用程序中的类似行为,这也开始发生(同样令人讨厌)。 解决方法是我相信它可以忽略对话并继续工作。我不知道其他人(或其他人)是否遇到过这个问题? 我也开始解决这个问题。 / p> 在搜索时,我将这个问题翻译为 https://code.google.com/p/chromium/issues/detail?id=335248 。 我最好的想法是错误与以下内容相关: 带Aero主题的Windows 7/8 滚动条页面(例如在开发人员控制台中) 带弹出窗口的页面(特别是Window.open()调用) 我猜他们会将修正版推入版本33中,也许会离开稳定版* 32(尽管我希望不会)。 所以有几个选择: 切换到Aero Theme直到版本33稳定 升级到测试版频道,即版本33 点击每当chrome开发人员工具处于打开状态时,每隔30秒发送一次Wait按钮。 更新: Chrome已向32版稳定版频道发布了一个修补程序。 http://googlechromereleases.blogspot.ro/2014/01/stable-channel -update_27.html 感谢@probackpacker引起我的注意。 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? 解决方案 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 ThemeScrollbars 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 stableUpgrade to the beta channel, i.e. version 33Click 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.htmlThanks to @probackpacker for bringing it to my attention. 这篇关于Chrome浏览器“无响应页面”假阳性(自Chrome 32以来)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持! 上岸,阿里云!
08-21 11:18