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 118581 - Merged Paths for Heap Dumps
Summary: Merged Paths for Heap Dumps
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-11 17:02 UTC by Alexander Kouznetsov
Modified: 2012-06-21 15:53 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-10-11 17:02:11 UTC 
Users are really missing the following view for heap dumps: Merged Paths for an object
    * Merged Paths shows the tree of classes that hold references to instances of any given object. It doesn't show
paths from individual objects, but paths from multiple objects grouped by class. This view gives you an idea which
classes retain most of instances of any given class
Comment 1 Tomas Hurka 2007-10-11 19:03:58 UTC 
Where is such user feedback available?
Comment 2 Alexander Kouznetsov 2007-10-12 09:56:11 UTC 
Answered via e-mail.
Comment 3 Egor Ushakov 2012-06-21 15:18:07 UTC 
In CND team we want this feature very much. Now we analyze huge snapshot and it is impossible to walk through 80M instances to find out where most of them used.
Comment 4 Tomas Hurka 2012-06-21 15:26:55 UTC 
(In reply to comment #3)
> In CND team we want this feature very much. Now we analyze huge snapshot and it
> is impossible to walk through 80M instances to find out where most of them
> used.
Until this is implemented, you can pick a few random ones. This approach works fine in most of cases. BTW: Is your heap dump available somewhere?
Comment 5 Egor Ushakov 2012-06-21 15:53:46 UTC 
(In reply to comment #4)
> (In reply to comment #3)
> > In CND team we want this feature very much. Now we analyze huge snapshot and it
> > is impossible to walk through 80M instances to find out where most of them
> > used.
> Until this is implemented, you can pick a few random ones. This approach works
> fine in most of cases. BTW: Is your heap dump available somewhere?

that's what we do...