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.

Bug 151331 - Heap Dump should have special facility (like References) which helps to understand what prevents an object to be GC
Summary: Heap Dump should have special facility (like References) which helps to under...
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@profiler
: 153985 (view as bug list)
Depends on:
Reported: 2008-10-24 20:52 UTC by Nikita Krjukov
Modified: 2010-09-06 10:37 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Krjukov 2008-10-24 20:52:31 UTC
Now it is possible but unfortunately very difficult to find out which object's chain (to GC Root) holds an object from
being garbage collected. Usually there are a few (1-2-3) reasons. But the References view (Heap Dump) shows all
references including those, which have WeakReference (and others) in theirs path to GC Root. 

I think it can be a view like the References view, which shows only those references, which comes to GC Root and don't
have weak references in the path. The References view can be used itself, but it should be filtered. It seems I have
seen such feature in JProfiler and it is very helpful. 

Now there is only "Show Nearest GC Root". It helps but not very much. Moreover, it works not very obvious. It is not
clear if it depends on the selected References tree's node or node. Sometimes it is disabled. I couldn't understand why. 

I think the searching memory leaks is the main target of memory profiling. So I set priority to P1. 
Moreover, I believe it is not very difficult to implement. 

I tried looking for the same issues. Probably the following are related: #113982 #120913 #83969
Comment 1 Jiri Sedlacek 2010-09-06 10:37:41 UTC
*** Bug 153985 has been marked as a duplicate of this bug. ***