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.
Currently during simple memory profiling the Profiler monitors just 1/10th of allocated objects (this is covered in the documentation, but users don't necessarily read it [thoroughly]). While this mechanism dramatically reduces the performance overhead, the resulting measured numbers may be confusing if the user doesn't know about this feature. It has been suggested that we make the proportion of the monitored object visible and user- adjustable in the "Analyze memory usage" profiling menu item.
Agreed with improving the visualization on the Select Task panel. BTW. back in December we were talking about other strategies wrt memory profiling results and overhead minimalization, like turning on/off allocation stack trace, or counting all instances (and reporting them) but taking allocation stack for 1/n of them, and then reporting the 1/n in the results allocation tree. Shall we address this as part of this issue as well?
Let's postpone more advanced changes to M6 (I think our initial intent was to get M5 out of the door quickly, right?). These changes will need more thinking, and may lead to some system destabilization that is undesirable if M5 is to be released soon.
Postponing to M6, will try to do some improvements in M5 by adding the 1/n control to the predefined memory task
I suggest that we consider this issue closed for now. Later we can open a separate enhancement, which will specify exactly what improvements to memory profiling we want to implement.
old issue, closed