On 18/03/16 21:05, Andrea Aime wrote: > On Fri, Mar 18, 2016 at 1:40 AM, Ben Caradoc-Davies <[email protected]> > wrote: >> I increased the nightly build heap to -Xmx2048m to fix them. I usually >> need this flag to build -PcommunityRelease locally. It does seem excessive. > Wow yeah it does. Thanks for fixing the nightly builds. > Do you have any clue as to why it's going OOM, and if any particular module > is responsible for that?
Sorry, no idea. Perhaps it is related to running four concurrent build threads? Community modules are a more independent of each other so they might be more likely to build in parallel. In each thread javac may need to load most of the project into its classpath. Does maven-compiler-plugin use a separate classloader for each thread? But we fork javac so how can it be to blame? I also have the horrible feeling that jar collection is performed in memory. It is not the tests failing as these are a forked subprocess and we see OOME when building with -DskipTests -PcommunityRelease. I will try a build with -X and see if I can spot the culprit. Kind regards, -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
