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

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Jan 5 14:40:22 PST 2011


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

--- Comment #21 from jianwu <jianwu at sdsc.edu> 2011-01-05 14:40:20 PST ---
status update: after the check in yesterday at version 26623, now there is no
big memory leak for window open and close in Kepler and Reporting suite. My
tests show Kepler memory usage is 42MB after starting (with GC) for reporting
suite. Memory usage changed to 65MB after open a big workflow (with GC and open
from xml). After closing the workflow, memory usage is back to 44MB (with GC).

Yet workflow open and close is just one basic function for Kepler. Many other
functions still need to be tested, such as workflow closing after execution,
reporting view, run manager and etc. My tests today also found memory leaks. 

Also my tests for bug http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4801
still show memory leaks. Kepler memory usage is around 100MB after the
tpc01-buffalo-tb.kar is open and closed. Two possible reasons are 1) tens of
data connection threads are created in the beginning; 2) some actors in the
workflow got initialized during the opening but not released during closing.

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


More information about the Kepler-dev mailing list