Negative performance implications of using GWT emulated stack trace

Question

For ease of reporting client side GWT issues, the emulated stack trace is very valuable. However when I activate this feature, there are serious performance implications (I've had to back it out twice now)

Specifically, it has been observed that while the GWT application is being downloaded, the IE browser appears to freeze and do nothing for 15 seconds or more when the emulated stack trace feature is enabled.

Has anyone else experienced this, and if so were you able to resolve the performance issue?

Answer 1

At compile time, generate permutations for both native and emulated stack traces in *.gwt.xml: <set-property name="compiler.stackMode" value="native,emulated" />

At run time, make your selection, e.g. <meta name="gwt:property" content="compiler.stackMode=emulated" />