Permgens are like JVM hanging completely -- there's not much the test runner can do (because everything is typically and effectively dead on the Java side of things).
It needs to be solved in the code; there's very likely multiple classloaders being loaded and something prevents them from being released. Dawid On Fri, Jul 24, 2015 at 9:23 AM, Uwe Schindler <u...@thetaphi.de> wrote: > Hi, > > (this is unrelated to my permgen improvements yesterday about the Ant build). > This mail is about the test runners. I had to kill builds on MacOSX quite > often because the test runner went into a permgen error. The problem: Killing > the jenkins job was not enough, because the test runners not even reponsed to > sigterm. You had to kill them (kill -9) it, otherwise it never dies. There is > nothing the test runner can do, because it died completely. > > The reason is that on JDK 1.7 there is still permgen used and the test seem > to load too many classes or whatever, no idea: > http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/2492/ > (search for permgen n the logs). > > Please fix this before release, this happened quite often the last 2 weeks! > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
