As already said the first thing you should do is to use -strict. This makes sure GWT compiler does not ignore compile errors. Given you have 12 compile errors, you want to fix them first.
Next it looks like you have a lot of split points if you have 856 *.cache.js files. Given that 817 of these files are less than 100kb and these files are usually gzipped by the web server before transferring to the client browser, you should try to reduce the amount of split points. I could imagine that analyzing the code for split point calculation might be the culprit. There is also an -optimize option for the GWT compiler with values 0 - 9 (0 = no optimizations, 9 = aggressive). I don't recall the default value but if it is 9 then it will do an optimize loop on the code AST until the AST does not change anymore. In rare cases this can end up in an endless loop. Using -optimize 8 usually fixes the issue as the compiler will do at most 8 optimize loops then. So you might want to try that as well. I have a compiled app that is roughly half the size of yours (about 15 MB) and it compiles fine with just 8 GB Ram. But it only has about 20 split points. Using 64GB seems overkill in your case. Maybe you could also try making a heap dump and analyze it in Eclipse memory analyzer to see what is consuming all your heap memory. However analyzing a 64GB heap dump won't be fun either. -- J. [email protected] schrieb am Dienstag, 1. März 2022 um 16:27:41 UTC+1: > Hi, > > We are having a quite big project, every thing was going in control but > from last few days our GWT project is crashing while building WAR (with > error out of memory). > "*Compiling module project2.**Project2* > > > > > * Validating units: Ignored 12 units with compilation errors in > first pass.Compile with -strict or with -logLevel set to TRACE or DEBUG to > see all errors. Compiling 1 permutation* > * Compiling permutation 0...* > > *[ERROR] OutOfMemoryError: Increase heap size or lower > gwt.jjs.maxThreadsjava.lang.OutOfMemoryError: Java heap space*" > > *System (PC) configuration on which we are building WAR is:* > OS = WINDOWS SERVER 2019 > PROCESSOR = XEON (R) CPU E3-1225 V5 @ 3.3Ghz > CORE = 4 > RAM = 64GB > HARD DISK = HDD > C (OS drive) = 203GB free of 243GB > E (drive) = 501GB free of 642GB > F (drive) = 467GB free of 976GB > > *rest please find the PC images attached.* > > > *GWT build configuration is:* > gwt.module=project1.Project1 project2.Project2 > gwt.output.dir=/org.yournamehere.Main > gwt.compiler.output.style=OBFUSCATED > gwt.compiler.jvmargs=-Xmx61440m > gwt.compiler.local.workers=1 > gwt.compiler.logLevel=INFO > gwt.shell.output.style=OBFUSCATED > gwt.shell.logLevel=TRACE > > gwt.shell.jvmargs=-Xmx61440m > gwt.shell.java= > gwt.version=2.6 > gwt.shell.code.server.port=9997 > gwt.shell.port=8888 > > *rest please find the gwt.properties file attached.* > > > *WAR file info:* > > *.WAR (Size on disk) = 577MB > > *project1.Project1* > *.gwt.rpc (count) = 1 > *.gwt.rpc (size) = 8kb > *.cache.html (size) = 335kb > *.nocache.js = 6kb > > *project2.Project2* > *.gwt.rpc (count) = 876 > *.gwt.rpc (size) = 9.76MB > *.gwt.rpc (max) = 19kb - 11kb (158 files), 10kb - 8kb (718 files) > *.cache.html (size) = 1713kb > *.nocache.js = 6kb > deferredjs\4D7A0074D70FA749A45BC16CDEAAFFE3\*.cache.js (count) = 856 > deferredjs\4D7A0074D70FA749A45BC16CDEAAFFE3\*.cache.js (size) = 28.6MB > deferredjs\4D7A0074D70FA749A45BC16CDEAAFFE3\*.cache.js (max) = 4043kb(1 > file), 446kb - 101kb (38 files), 98kb - 1kb (817 files). > > > > *WE REQUEST TO ALL PLEASE HELP! AS DELIVERY OF THE WAR IS REQUIRED ON > URGENT BASIS.* > > > > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/ef9256e5-177b-4c09-830d-437090f81d08n%40googlegroups.com.
