Hi all. We have a fairly large GWT application (~20MB OBF). Recently (last week I believe) we started to encounter a RangeError: Maximum call stack size exceed in Chrome in our deployed application. The error does not occur in FF or IE. I downloaded older versions of Chromium and confirmed that the application still works, so I'm guessing there was a recent update to Chrome (47) that caused the issue.
There is no problem in SDM, and after playing around with the optimization level, found that at level '0', the app loads. At 1-9, the exception is thrown, and from what I can tell by setting a breakpoint on exception, it does not appear to be too deep in a call stack. I realize that this is not a bug per-se of GWT, but I would think (hope) that the GWT compiler could account for browser limitations when performing optimizations, to not optimize otherwise working code into code that won't run. Would love to supply more information if needed. I'm hoping others have discovered the same issue, and that there is an easy solution that can squeeze into the 2.8 release. Thanks in advance, Josh -- 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/2ad014eb-f4b0-40fc-b133-9b589a6cb0f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
