Hello, we have a very large GWT project with only client code (approx. 1 million LoC , everything in a single module) and an Jenkins job up running which uses ant to build the project and to deploy the code on our test environment and productive servers. It uses about 2 GB as Heapsize value for the builds. With GWT 2.6.1 the builds take about 12-15 minutes to finish (with 8 permutations: gecko and webkit, german and english locales and debug messages off / on) but after upgrading to 2.7.0 they're always failing due to OutOfMemory errors. To get them pass I have to increase heapsize to a minimum of 4GB or better 6GB. I tried already to turn off the compiler optimization (level 0 instead of 9) and tested some options like draftCompile, but still the builds are failing.
What happens there during compilation so that it needs at least the double of memory space? Do you have some suggestions so I can optimize my builds (run faster, need less memory)? Thanks in advance, Paul -- You received this message because you are subscribed to the Google Groups "GWT Contributors" 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-contributors/38149b55-9080-469f-8456-0c55dacf7ed9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
