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 119408 - Improve usability when tracking memory leaks
Summary: Improve usability when tracking memory leaks
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-18 20:25 UTC by _ gtzabari
Modified: 2016-11-09 13:50 UTC (History)
0 users

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 _ gtzabari 2007-10-18 20:25:41 UTC 
When an application leaks a very common class type (such as java.lang.String) it is extremely difficult to track down
the source of the leak. I see two problems:

1) Heap dump: ideally I want to find a leaked object, then look at who is referencing it. Unfortunately, the JDK
allocates thousands of String objects so it becomes impossible for me to track down a String object leaked by my
application.

2) Compare snapshots: ideally I want to "compare snapshots", then right-click on a node and "Show Allocation Traces".
Unfortunately, the "compare snapshot" feature does not display traces.

Fixing these usability issues will go a long way towards helping users track down memory leaks. For #1 I would expect to
be able to filter objects based on their allocation trace or something similar.
Comment 1 Tomas Hurka 2007-10-19 06:30:01 UTC 
Note that allocation stacktraces are not available in HPROF heap dumps.
Comment 2 Jiri Sedlacek 2016-11-09 13:50:04 UTC 
Hopefully addressed by the new profiler - HeapWalker displays String values, memory snapshots can be compared including allocation stacks.