When there were leaks from static classes, we added a checker to
LuceneTestCase that looks for RAM > N and fails with debugging information.

I wonder if some similar check is possible for this case (to make it easier
than going thru heapdumps, and to find issues before crash-time)...

On Sun, Jul 7, 2013 at 4:10 PM, Uwe Schindler <[email protected]> wrote:

> Another one:
> http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/6385/testReport/junit/junit.framework/TestSuite/org_apache_solr_request_SimpleFacetsTest/
>
> Had to be killed with kill -9
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
>
> > -----Original Message-----
> > From: Uwe Schindler [mailto:[email protected]]
> > Sent: Saturday, July 06, 2013 10:16 PM
> > To: [email protected]
> > Subject: RE: Several builds hanging pecause of permgen
> >
> > Another one:
> > http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/6375/console
> >
> > I was only able to kill the JVM with kill -9 I am sure, it's horrible
> slowdoop!
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [email protected]
> >
> >
> > > -----Original Message-----
> > > From: Uwe Schindler [mailto:[email protected]]
> > > Sent: Friday, July 05, 2013 3:59 PM
> > > To: [email protected]
> > > Subject: Several builds hanging pecause of permgen
> > >
> > > Several Jenkins builds now hang because of permgen. The runner JVM is
> > > dead (can only be killed by -9), last example:
> > >
> > > http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/6360/console
> > >
> > > -----
> > > Uwe Schindler
> > > H.-H.-Meier-Allee 63, D-28213 Bremen
> > > http://www.thetaphi.de
> > > eMail: [email protected]
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected] For
> > > additional commands, e-mail: [email protected]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected] For additional
> > commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to