You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2004/10/08 18:05:56 UTC
DO NOT REPLY [Bug 27573] -
Memory Leak
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27573>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27573
Memory Leak
------- Additional Comments From woolfel@yahoo.com 2004-10-08 16:05 -------
no additional report was added. Since I've profiled jmeter in OptimizeIt over 2
dozen times for the monitor, distribution graph, and webservice sampler, I'm
pretty confident the issue is not JMeter. Without further details, it's hard to
figure the exact cause. the only thing I can think of which could cause memory
leak is if the user only has 128Mb of ram and the system is disk caching.
it is possible with heavy disk caching the heap gets fragmented and produces
results equivalent to a memory leak. I've also seen this type of behavior in
other VM environments like .NET. If that is the case, it is really a hardware
issue. If there isn't enough memory, there's not much a program can do.
especially VM environments.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org