Created attachment 581285 [details] Show load times for each gwt compile option Description of problem: The Pretty option gives us the best performance option while still maintaining the ability for stack traces. It reduces the application size by 1/3. See attachment for App Initial Download Times.
master commit: e271195 As the above report confirms that the pretty option is the best size/performance option while still providing usable stack traces with source file names and line numbers. See http://code.google.com/p/google-web-toolkit/wiki/WebModeExceptions for options. This choice should eliminate the option for OBF with emulated Stack traces. So I'm removing the following code from CoreGui.gwt.xml (it is here for future reference): <!-- the emulated stack allows us to run in OBF compiled script and gives us stack traces for debugging (we will investigate this more in the near future). see: http://code.google.com/p/google-web-toolkit/wiki/WebModeExceptions <set-property name="compiler.stackMode" value="emulated" /> <set-configuration-property name="compiler.emulatedStack.recordLineNumbers" value="true" /> <set-configuration-property name="compiler.emulatedStack.recordFileNames" value="true" /> -->
Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.