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 121924 - Don't remove garbage collected objects from Memory Liveness results
Summary: Don't remove garbage collected objects from Memory Liveness results
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
Keywords: VISUALVM
Depends on:
Reported: 2007-11-14 16:21 UTC by Alexander Kouznetsov
Modified: 2011-11-02 20:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

log related bug (309.53 KB, application/octet-stream)
2011-06-13 06:52 UTC, ErRadhikaSharma

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-11-14 16:21:58 UTC
Product Version: NetBeans IDE 6.0 RC1 (Build 200711140000)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

Currently it is designed that Live Results don't show objects which are fully garbage collected during the profiling in
Liveness Profiling mode. It seems to be natural to show such objects with "0" in Live Objects column, so user could
track Allocated Objects and Avg. Age columns. This could be an option to show/hide such objects.

It looks strange and non-working when some objects are shown in Live Results and then disappear when user presses Take
Snapshot button, producing also an empty snapshot.

See also issue 84624
Comment 1 Alexander Kouznetsov 2007-11-15 14:53:17 UTC
It looks to me like a defect, since I got a lot of classes with zeros in Live Objects and Live Bytes and they were still
shown in Live Results. Probably it was caused by use of "Stop Profiling" feature before modify profiling.
Comment 2 J Bachorik 2008-03-29 12:15:25 UTC
changing milestone
Comment 3 ErRadhikaSharma 2011-06-13 06:52:52 UTC
Created attachment 108870 [details]
log related bug

there is an error related to IDE's configuration