We're trying to compile a very large GWT project that generates in non obfuscated mode(PRETTY setting) around 41MB of nocache.js per module.
It works fine but when enabling stack trace emulation(to have deobfuscated exception stack traces in Eclipse through SDBG), compilation gets stuck at this line(full log atached):
Linking per-type JS with 11838 new/changed types.
Sometimes there's this error:
OutOfMemoryError: increase heap size or lower gwt.jjs.maxThreads
Having increased the heap size considerably(2GB), this error goes away but compiler remains stuck at that line for a very long time.
We also ran the above with -logLevel DEBUG but compiler gets stuck on same line, with no additional information.
We've tried this scenario with same result on GWT 2.8.0 Beta1, RC1 and RC2.
Do you know if this is something due to our code base or something else?
Indeed, there are still some optimizations to do, we have many RPC services with generic types(List, Map, etc.) that generate a lot of permutations. We should use concrete types instead.
We plan to improve that.
Do you know how to further debug why this is happening?
Could it be due to something else than our RPCs, that maybe needs fixing on GWT-side?