Hi, I have a large GWT app deployed too, and didn't notice any problem with the new Chrome. Do you use any large GWT framework, such as Vaadin or GXT? Or any framework/lib outside GWT on the client side? Or maybe any native component?
On Wednesday, December 16, 2015 at 3:11:10 PM UTC-2, Joshb wrote: > > 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/2feb660d-37e5-4c2a-a6d2-bde9079d9259%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
