Re: memory leaks

From:

John Ersatznom <j.ersatz@nowhere.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Mon, 08 Jan 2007 05:03:52 -0500

Message-ID:

<ent4qv$v9i$1@aioe.org>

Jeff wrote:

The question I have is what can I use (profiler, debugger, etc.) to tell
me what variable(s) are the ones that are taking up enormous amounts of
memory? I've tried the Eclipse debugger and I notice that a list model
that I use gets bigger however the actual data stored in it is the right
amount with the remaining elements actually being set to null.

Might try forcing a garbage collection. Actually, it just suggests to
the JVM that it might be a good time to take out the garbage.

System.gc();

I'm not sure that's the problem here. The list model that's getting
bigger and clogging up with unused nodes is the problem, given that
apparently they aren't held with weak references of any kind. Either the
list is leaking in some screwy way, or it recycles a pool of nodes
internally but doesn't use SoftReference or similar to allow the gc to
get rid of these when space is getting tight.

This could be a JTree implementation issue.

Does the other application use JTree (or even Java at all)? If so, do
you have access to the source? See if they are doing anything different
with their JTree.

And by all means, give System.gc() a try; just don't expect much from it
but a lengthy pause in your GUI's response.