chrome 53 freezes my GWT 2.7 app

RT

unread,

Sep 26, 2016, 2:34:37 PM9/26/16

to GWT Users

The app was working fine for a year, and still works in IE and FireFox, but in Chrome 53 it seems to get frozen perhaps after a code splitting point. I can't debug because the Chrome tab is unresponsive. Is anyone else having issues in Chrome 53?

RT

unread,

Sep 29, 2016, 3:08:35 PM9/29/16

to GWT Users

Chrome 54 (Beta) works fine

Kirill Prazdnikov

unread,

Sep 30, 2016, 7:23:17 AM9/30/16

to GWT Users

Debugging in Chrome is broken for me.
It consumes 100% cpu and hangs.
I use an old Chrome to work.

Matt Sutterlin

unread,

Oct 26, 2016, 2:27:44 PM10/26/16

to GWT Users

I was actually about to open a new topic on this exact issue till i found this. We have a rather gwt large app, where we are at the point of setting our SDM VM args to -Xmx14g. All was working well until yesterday when I updated from Chrome 53 to Chrome 54. Now, everytime I try to hit a breakpoint in super dev mode, it actually hits the breakpoint in dev tools, the does its normal spinning (where its loading up the source maps), then after 3 seconds completely crashes the chrome tab with an Chrome Out of Memory Exception. Note: the app works fine in super dev mode as long as i dont hit any breakpoints. Also, I have plenty of free ram available. Im thinking this is an issue with Chrome itself, but figured I'd check here first. (let me know if I should break this out into its own thread)

Reply all

Reply to author

Forward