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.
Using the daily build from 2007-10-14 on JDK6u2, running on Ubuntu 7.04 Following the instructions in this demo script: http://wiki.netbeans.org/wiki/view/HeapWalkerDemo, I generated a small heap dump. Clicking the Analysis tab in the heap walker, I then ran these rules: Duplicated Strings HashMap Histograms Overallocated Strings All three of them seemed to find something, but they provided no details. The output from the Duplicated Strings rule was: Total waste: 45236B, distributed by domain source: Total instance count: 593, size: 45236 ---- The output from the HashMap Histograms rule was: Total instance count: 227, size: 205498 ---- And the output from the Overallocated Strings was: Wasted 6648B on overallocated Strings Total instance count: 241, size: 6648 ---- Shouldn't there be detailed information listed to show the class type/field names for the root objects that were found? Or is the problem here that *nothing* could be found that was not from java.* or javax.*? If that is the case, then maybe a message should be written out to let the user know that. As it is now, it seems kinda' confusing. I have seen this on other heap dumps as well.
Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode.
Target milestone cleanup.
Milestone cleanup: future->next
Lowering priority as the OQL console is now the preferred way to analyze the heap dump. The Analysis view is still just a kind of experimental feature currently in "stand by" mode.
We do not plan to fix it. Use OQL console instead.