Hi, If it helps, you might avoid the crash by installing the monitoring plugin, and triggering garbage collection once the memory is approaching the maximum allocated heap size. This is a workaround until someone is able to diagnose the root cause. I have an open issue : https://issues.jenkins-ci.org/browse/JENKINS-34573 but thought I'd run the suggestion.
On Thursday, 12 May 2016 10:59:30 UTC-4, Ugo Bellavance wrote: > > > > On Thursday, May 12, 2016 at 10:49:02 AM UTC-4, Ugo Bellavance wrote: >> >> >> >> On Thursday, May 12, 2016 at 4:31:37 AM UTC-4, Stephen Connolly wrote: >>> >>> I am suspecting JENKINS-34213 may be your issue. >>> >> >> I have new information. We installed the monitoring plugin and I started >> using VisualVM. I can see that, while I use -Xmx10752m, it only uses a >> little less than 8 GB. Is there a problem with my configuration? I also >> got a heap dump. >> >> JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true >> -Dcom.sun.management.jmxremote -Xmx10752m" >> >> (in /etc/sysconfig/jenkins on RHEL6). >> >> > Links for images: > > http://picpaste.com/pasted-1463060174-109834-vyo0x5qe.png > http://picpaste.com/usedMemory-YYL6OQhQ.png > > > -- You received this message because you are subscribed to the Google Groups "Jenkins 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/jenkinsci-users/4ccc0462-d514-4f10-ba4e-de0e0b4fa82e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
