You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-users@jakarta.apache.org by Matthew Cooke <mp...@lineone.net> on 2004/05/05 12:21:22 UTC

Memory leak problem

Aaron,

I found increasing the JVM to 800meg only delayed the out of memory 
problems. I profiled for a while on the production machine but this only 
revealed a lot of stacktraces accumulating and these were eventually 
thrown away during a GC.
I tried disabling the memory shrinker like you suggested and so far the 
JVM hasn't requested an increase above it's starting allocation of 80Meg 
which is promising.

It's still a bit early to be 100% sure, but I was wondering what the 
memory shrinker does exactly? Is this the code that keeps the cache 
below the maxobjects setting?

Kind Regards,
Matt.

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org


RE: Memory leak problem

Posted by Aaron Smuts <aa...@wisc.edu>.
The shrinker periodically wakes up and looks for expired elements.  

It doesn't keep the memory under the max.  That's done when you put an
item into the cache.

I think I saw that you had the shrinker come on every few seconds,
correct me if I'm wrong.  I was afraid that it would keep references to
everything if it was always running.  Now I'm not sure that could
happen.

Aaron

> -----Original Message-----
> From: Matthew Cooke [mailto:mpcooke3@lineone.net]
> Sent: Wednesday, May 05, 2004 5:21 AM
> To: Turbine JCS Users List
> Subject: Memory leak problem
> 
> Aaron,
> 
> I found increasing the JVM to 800meg only delayed the out of memory
> problems. I profiled for a while on the production machine but this
only
> revealed a lot of stacktraces accumulating and these were eventually
> thrown away during a GC.
> I tried disabling the memory shrinker like you suggested and so far
the
> JVM hasn't requested an increase above it's starting allocation of
80Meg
> which is promising.
> 
> It's still a bit early to be 100% sure, but I was wondering what the
> memory shrinker does exactly? Is this the code that keeps the cache
> below the maxobjects setting?
> 
> Kind Regards,
> Matt.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-jcs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org