Thanks Jens, 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. On Tuesday, March 29, 2016 at 5:36:29 PM UTC-4, Jens wrote: > > > The biggest problem is that Chrome doesn't give ANY stacktrace, nor does >> it allow for breaking on error. I've tried compiling with 'pretty' so I >> could breakpoint on error and figure out the offending code, but it won't >> work. >> > > Chrome can pause on any JavaScript error thrown, caught and uncaught ones. > Go to the sources tab in Chrome DevTools, hit the small "pause" icon on the > right side and check the "pause on caught exceptions" checkbox. Chrome > should then pause on ANY exception thrown, so you would need to check if > its the "RangeError: Maximum call stack size exceed" or not. > > If Chrome still does not pause even though you get the mentioned error > then you have to talk to the Chrome guys by opening an issue to ask them > how to debug that situation. Adding lots of log statements doesn't seem to > be the solution. > > -- 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/8b8c9ead-d52b-4d51-9d1a-6b6d9a28e5d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
