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.
There is a significant memory leak left with each Project / Properties dialog opening and closing. See the attached OptimizeIt screenshot of ProjectCustomizer$Category reference path. I looked at reference paths of various objects of the leak and they all seemed to go through ProjectCustomizer$Category.
Created attachment 27165 [details] OptimizeIt screenshot
For completeness, I recorded this when repeatedly invoking jEdit project Properties action. So, this is J2SE project. I did not try with other project types.
[build 200511211900, jdk 1.5.0_05, linux FC3]
I think that the main problem (the number of categories grows with opening the project customizer dialog) is the same as in issue #67845: the projectuiapi holds categories forever. The J2SE project holds only the last used categories for each project, which should be more or less OK, I think (the amount of categories should no grow). Lets wait for issue #67845 (should be fixed tomorrow, if everything goes OK) and do the measurement again.
I was able to reproduce the leak before fixing issue #67845. I am not able to reproduce it after fixing issue #67845. Please reopen with new data if you are still able to reproduce the leak. Thanks.
The cummulating leak is gone. After the first invocation of the customizer the various org.netbeans.modules.java.j2seproject.ui.customizer.* objects are created and stay on heap since then. But this is acceptable I believe.