On Thursday, May 12, 2016 at 2:01:41 PM UTC-4, Raymond Accary wrote: > > 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. > >> >> Have anyone monitored the JVM with VisualVM? I have found that it looks like a specific memory pool may be filling up: Old Gen. I'm trying now with:
-Djava.awt.headless=true -Dcom.sun.management.jmxremote -Xms10752m -Xmx10752m -XX:NewRatio=10 We'll see in a few days. In the last few days, the problem have occured each morning at around 4:45. I'm not sure if the same jobs run on the week-ends as well. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/19e79b21-0ade-4cd7-a681-ddbadbfee73b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
