This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I've run performance test suite with focus on possible memory leaks. I reused the same test cases (tests and test infrstructure) as we use for measure UI responsiveness. http://performance.netbeans.org/qa/Performance.html I would like to point out here, there is no call for you to fix reported memory leaks, first of all leaks must be find, this is only hint, there are many places where leak can be found (test harness, test case, xtest , jemmy, jelly....). Performance team members should go through all reported issues and reassigne it against appropriate person/module or after short investigation close it with appropriate comments. PerformanceTestCase uses next : ------------------------- runGC(5); initialize(); repeate X-times { prepare(); open(); close(); runGC(3); Runtime runtime = Runtime.getRuntime(); memoryUsage[i] = runtime.totalMemory() - runtime.freeMemory(); } findMinimumOfMeasuredMemoryUsages(); logDeltasAgainstMinimumMemory(); ------------------ and runGC(X) is implemented this way : ------------- public void runGC(int i){ for(int gc=0; gc < i; gc ++){ try{ System.runFinalization(); System.gc(); Thread.currentThread().sleep(500); System.gc(); Thread.currentThread().sleep(500); System.gc(); Thread.currentThread().sleep(500); }catch(Exception exc){} } } -------------------
Now we are using assertGC in commit validation as well as in various qa-funcational tests.
v/c