Author: norman
Date: Wed Aug 23 09:54:14 2006
New Revision: 434078
URL: http://svn.apache.org/viewvc?rev=434078&view=rev
Log:
Language fixes
Modified:
james/server/trunk/src/site/xdoc/upgrade_instructions_2_3.xml
Modified: james/server/trunk/src/site/xdoc/upgrade_instructions_2_3.xml
URL:
h
I strongly recommend YourKit... you can get a free 14 day trial, do
two memory snapshots and run a diff to see what objects are leaking.
I think that or some other true profiling tool is necessary to spot
leaks.
agreed, but at first I'd like to reproduce the case.
--
On 8/23/06, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
be careful with interpreting this value. the JVM is _not_ required to
release memeory as soon as it is no longer referenced! so (maybe) it
keeps appearing under "memoryUsed" although it _could_ be garbage
collected.
I share Bernd's caution
