Find solution
How to debug chrome manifest.json?

What can I do to make GWT debugging in Chrome less painful?

  • One problem is of "plugin not responding" which I got rid by --disable-hang-monitor. Time it takes for app to execute in debug mode seems a lot and I was wondering if I can do something to bring it down ? Since GWT and Chrome come from Google, I was hoping to use some clever techniques to make this whole debugging thing little faster.

  • Answer:

    Ray Cromwell, the GWT lead is saying Chrome updates to fast and they can’t keep up the plugins.  Here is a link to the bug report and Ray's comment. http://code.google.com/p/google-web-toolkit/issues/detail?id=5778#c65 My issue is Chrome keeps on crashing when running in DevMode locally.  I've had to use IE (shudder) to make changes to my GWT apps. :( I am hopeful that the new SuperDevMode that's coming in GWT 2.5 will make development a little faster and actually work in Chrome. --Vinny

Vinny Carpenter at Quora Visit the source

Was this solution helpful to you?

Related Q & A:

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.