简体繁体 English

chrome下的GWT调试缓慢

[英]GWT debugging slow under chrome

原文 2014-05-15 09:23:13 0 1 java/ google-chrome/ gwt

Why debugging GWT is incredibly slow under Chrome, whereas the speed is reasonable under Firefox. 为什么在Chrome下调试GWT的速度非常慢，而在Firefox下却是合理的。 (Firefox causes pain in its way as well. Since version 27 it doesn't even support GWT debugging plugin anymore.) （Firefox也引起痛苦。自版本27起，它甚至不再支持GWT调试插件。）

GWT debugging in Chrome has been slow for at least two years and it's not improving. 在Chrome中进行GWT调试至少两年来一直很慢，而且没有得到改善。 So what is causing it and any solutions? 那么，是什么原因导致的呢？ I am also a web developer and I'm certain most cases Chrome is much faster and its Dev Tool is just awesome. 我也是一名Web开发人员，我敢肯定大多数情况下Chrome的速度要快得多，其开发工具也很棒。

1 个解决方案

This is due to Chrome sandboxing plugins (so they don't have access to your computer's resources besides what Chromes allows), so passing things from the web page to the plugin (and back) is slower than in other browsers that run plugins in the same process (ie less securely). 这是由于Chrome沙盒插件（因此Chrome不允许的话，它们无权访问您计算机的资源），因此，将网页中的内容传递到插件（和返回）比在其他浏览器中运行插件的浏览器要慢相同的过程（即不太安全）。

That being said, Chrome will soon remove support for NPAPI plugins too, so DevMode won't work there either. 话虽如此，Chrome很快也会取消对NPAPI插件的支持，因此DevMode也将无法在其中运行。 Try SuperDevMode , and keep in mind it'll get a perf boost in GWT 2.7, to be released in a couple months. 尝试SuperDevMode ，请记住，它将在GWT 2.7中获得性能提升，并将在几个月后发布。