<div dir="ltr"><div><div><div>forkJvmArgs used to be "-Xmx2G" before ISPN-8478. I reduced the heap to 1G because we were trying to run the build on agent VMs with only 4GB of RAM, and the 2GB heap was making the build run out of native memory.<br><br></div>I've yet to see an OOME in the core tests, locally or in CI. But I also included -XX:+HeapDumpOnOutOfMemoryError in forkJvmArgs, so assuming there's a new leak it should be easy to track down in the heap dump.<br><br></div>Cheers<br></div>Dan<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 14, 2018 at 11:46 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey all,<br>
<br>
I'm having OOMs running the tests of infinispan-core.<br>
<br>
Initially I thought it was related to limits and security as that's<br>
the usual suspect, but no it's really just not enough memory :)<br>
<br>
Found that the root pom.xml sets a <forkJvmArgs> property to Xmx1G for<br>
surefire; I've been observing the growth of heap usage in JConsole and<br>
it's clearly not enough.<br>
<br>
What surprises me is that - as an occasional tester - I shouldn't be<br>
the one to notice such a new requirement first. A leak which only<br>
manifests in certain conditions?<br>
<br>
What do others observe?<br>
<br>
FWIW, I'm running it with 8G heap now and it's working much better;<br>
still a couple of failures but at least they're not OOM related.<br>
<br>
Thanks,<br>
Sanne<br>
______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br>
</blockquote></div><br></div>