[kepler-dev] [Bug 5095] test kepler and wrp for memory leaks

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5095

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cxh at eecs.berkeley.edu
    Estimated Hours|0.0                         |100.0

--- Comment #1 from Christopher Brooks <cxh at eecs.berkeley.edu> 2010-07-16 08:44:14 PDT ---
How I've fixed memory leaks in the past is by writing Java test cases that
illustrate the bug and then using commercial tools like JProfile to track
down the bug.  Eclipse has a memory leak analyzer at
http://www.eclipse.org/mat/.

It is also easier to track down leaks in non-gui code first.  Gui code
tends to leak because of underlying issues in the JDK.  For example, applets
were leaking under JDK1.5 on the Mac because of an internal Apple class
kept a reference to something.

For information about a leak from last year, see
http://chess.eecs.berkeley.edu/ptolemy/listinfo/ptolemy/2009-June/011591.html

Brian Hudson recently pointed out a leak in the MoMLFilter, which I'm taking
a look at.

Tracking down memory leaks can by time consuming, I'm putting this at 100.0
hours.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.