Negative effects of using emulated GWT stack trace

To facilitate reporting of client-side GWT problems, emulated stack tracing is very valuable. However, when I activate this feature, there are serious performance implications (I had to cancel it twice)

In particular, it was noticed that when the GWT application loads, the IE browser freezes and does nothing for 15 seconds or more when the emulated stack trace function is enabled.

Has anyone else experienced this, and if you could solve a performance problem?

+5
source share
1 answer

During compilation, create permutations for both native and emulated stack traces in * .gwt.xml: <set-property name="compiler.stackMode" value="native,emulated" />

At run time, make your choice, for example. <meta name="gwt:property" content="compiler.stackMode=emulated" />

+6
source

All Articles