> I'm familliar with the small 'pause' icon. It isn't being triggered. I > actually think that the error is being thrown before Chrome starts running > the code. Does that even make any sense? > In the chrome debugger, if I go to sources, the <CACHED>.js file doesn't > even show up under the js tab. > > I realize this is getting a little (or a lot) beyong GWT discussion. I > really don't understand why it is capped so low. Firefox is like 50k, and > it runs in every other browser. >
As its reproducible in your app I would suggest uploading your app (compiled using -style PRETTY) somewhere so it can be accessed by Chrome people and then open a Chrome issue. Without a JS stack trace we can't really do anything to workaround it in GWT. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/15a42000-bc95-4e14-bb89-8007d5b02443%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
