PERM OOM are related to the usage of Javascript in Loop conditions or other places (__javascript() or jexl or scripting languages (groovy ....)). In this case increasing to 128m generally fixes the issue, it's more a Sizing than a leak and until now my tests didn't show any memory leak in PERM zone.
Regards Philippe http://www.ubik-ingenierie.com On Mon, Jan 9, 2012 at 5:49 PM, Kirk Pepperdine <[email protected]>wrote: > > On 2012-01-09, at 2:57 PM, Flavio Cysne wrote: > > > Aloha, Art. > > > > What version of JMeter are you using? > > OOME is occurring when running JMeter GUI or non-GUI (-n parameter)? > > In GUI mode it may lead to OOME if you use a lot of Listeners. > > Have you tried changing mode to Batch in jmeter.properties? > > He has a perm space OOME. Listeners aren't in perm sapce. > > Regards, > Kirk > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cordialement. Philippe Mouawad.
