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.
The HeapWalker should be able to find the largest retained size objects across the entire heap. This is a CPU-intensive search, so the user interface should include an obvious "cancel" button. Also, it might be best to limit the search so that it stops automatically after finding the first 10 (or 20 or user-settable) largest objects. If the user wants to search for additional objects the HeapWalker should be able to find the next 10 (or 20) largest, and so on. The default sort size should be by retained size in descending order. The class type for each object should be displayed.
This lack of this feature is a really stopper for many users.
Agreed, this is a stopper for many users, but I guess maybe I am unclear on the purpose of P1. I thought P1 was reserved for application crash/data loss type issues, and this is not in that category. How about P2 as a compromise? :-)
Well, although the bug priority guidelines are more suitable for defects, there is a clear justification for this P1 issue: "Product feature does not work, no workaround exists". Applying this to enhancement we get "Product feature is not implemented, no workaround exists". You can also check the feedback I sent recently via e-mail. I don't object to leave this as P2.
Well, I don't understand this - does it mean that every not implemented FEATURE or ENHANCEMENT should be filed as P1?? That's definitely not the way how it works right now, otherwise we would have almost every RFE as P1.
You're right, I forgot to clearly mention the fact the according to user feedback this is a real stopper for a group of users.
*** Issue 155082 has been marked as a duplicate of this issue. ***
Already implemented.