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.
| Summary: | Merged Paths for Heap Dumps | ||
|---|---|---|---|
| Product: | profiler | Reporter: | Alexander Kouznetsov <mrkam> |
| Component: | Base | Assignee: | issues@profiler <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | vv159170 |
| Priority: | P2 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Where is such user feedback available? Answered via e-mail. 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. (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? (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... |
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