Re: [gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-03-29 Thread 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 .js file doesn't > even show up under the js

Re: [gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-03-29 Thread Joshb
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 .js file doesn't even show up under the

Re: [gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-03-29 Thread Joshb
One Idea I had was to see if it was possible to reduce the stack size in Safari or Firefox (or event IE) and see if it would give a better debug option (actually pause on exception). Does anyone know how to do that (change the call stack size) for one of those browsers? On Monday, March 28,

Re: [gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-03-29 Thread Joshb
Hi Colin, 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. We are using GWT 2.8-beta1, but I have the same issue

Re: [gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-03-28 Thread Colin Alworth
The only issue I know of that causes this is https://github.com/gwtproject/gwt/issues/8233 (and also apparently https://github.com/gwtproject/gwt/issues/8229), which is fixed in GWT 2.7. This issue was caused by invoking a method with many arguments, rather than wrapping those arguments in a list

[gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-03-28 Thread 'Marius Gerwinn' via GWT Contributors
Hi Josh, Just wan't to let you know that we're facing the same issue here. We also have a quite large app, using Errai and only experiencing the issue in the newer Chrome version. No workaround except disabling the optimisation yet. If you found something or want some more info about our setup

[gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-02-08 Thread Dominique L.
Hi, I have also a large GWT application. Recently, a strange error does occur only with a recent Chrome (48 ?) : "com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read property 'className' of null". To fix it, we just catch the exception silently... But i am a little

[gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-02-08 Thread Thomas Broyer
On Monday, February 8, 2016 at 5:25:37 PM UTC+1, Dominique L. wrote: > > Hi, > > I have also a large GWT application. Recently, a strange error does occur > only with a recent Chrome (48 ?) : > "com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read > property 'className'

[gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-01-22 Thread Joshb
Gilberto, I've done some more digging. Starting Chrome with --js-flags="--stack-size 6" makes the application work. I haven't played with the stack size to see what level breaks it. Interestingly, I've tried smaller modules, and the problem persists. We are using Errai, but the

[gwt-contrib] Re: New Error caused by recent Chrome Update: RangeError: Maximum call stack size exceeded

2016-01-17 Thread Gilberto Torrezan Filho
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