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.
When fighting with memory leaks I really miss ability to find "next path to GC root". As a result I need to run my application, that memory dump, open in profiler, find path to nearest GC root, fix the problem, and do that once again. One such run takes at least 10min, so my productivity is really low. It would increase significantly if I could fix all known leaks and only then rerun the application. The algorithm for finding more memoryleaks is simple, already implemented by NbTestCase.assertGC, however that system has troubles to identify all GC roots, that is why I need to use profiler then. Please implement "next GC root" or something similar in profiler as well. http://hg.netbeans.org/main/rev/ea0da89c5729
Ping?