Firstly upgrade to Java8 to get rid of the PermGen :) Secondly as this is permgen this sound like dynamic classes that are created for groovy may not getting disposed correctly so have some references somewhere - so I would use Java8 and get a heap dump and investigate from there. Something like the following should help for the java options when you start Jenkins. -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/disk2/dumps
I've seen memory issues in plugins that are fine in 99% of the installations that use them but that in 1% use them in a way that causes them to bloat memory - so don;t worry if no one else has seen it. Also - what are your memory options on the JVM - it may be its not leaking at all - but that the headroom is just too low (the defaults from Java are too low for anything other than a simple installation) /James On Thursday, March 10, 2016 at 6:08:32 PM UTC, Christian Lague wrote: > > As per https://issues.jenkins-ci.org/browse/JENKINS-33358 we experienced > some severe issues due to permgen memory leaks. This seems to be related to > use of Groovy, which is quite concerning given the use of it with Jenkins > (e.g. pipeiline plugin). This seems to be a serious issue but we have not > seen any other related issues. Anybody experienced the same? > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/cf7adb1d-a1f1-46c8-a555-4114f97bfb8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
