ot;, "live" and "reloading" features), but I'm too
lazy to make sure.
Cheers,
Larry
> -Original Message-
> From: Roberto Rios [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 05, 2004 3:35 PM
> To: [EMAIL PROTECTED]
> Subject: RE: S
Everybody is right. The saw teeth is around 3mb. The heap is around 9mb. So
after the GC runs, the available heap falls to 6mb.
As Yoah said this isn't a memory leak, since all the objects that area
created are garbage collected. I called it as a memory leak because even
with nothing running under
To: Tomcat Users List
Cc:
Subject: Re: Strage Behaviour - Tomcat Memory Leak
I've used JProfiler in the past and I found it somewhat unreliable,
since it is pretty heavy weight. I should say it was based on a half
dozen tests usin
> From: Peter Lin [mailto:[EMAIL PROTECTED]
> Subject: Re: Strage Behaviour - Tomcat Memory Leak
>
> I've use OptimizeIt in the past and tomcat without any
> requests shows flat memory usage. in other words constant.
Memory usage also depends on configuration options such a
I've used JProfiler in the past and I found it somewhat unreliable,
since it is pretty heavy weight. I should say it was based on a half
dozen tests using JProfiler and not a scientific evaluation.
it was the free eval version a couple years back. I find optimizeIt
more reliable for me and a littl
Hi,
It depends on the size of your saw teeth: if they're small (<2MB), it
can be attributed to anything including internal JVM optimizations.
HotSpot will move things around in memory even when no "activity" is
taking place.
Also, what you're describing is not a leak by definition, since the
memo
