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 62590 - Object age after reset results should reset to start from 0
Summary: Object age after reset results should reset to start from 0
Status: RESOLVED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 15:20 UTC by iformanek
Modified: 2006-10-23 16:40 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-08-18 15:20:56 UTC
If I hit "Reset Collected Results", should my average age start back
in the single digits?

Right now, I have a memory profile thats been running for > 50 hours,
and have the constant profiling results window open, so a GC is
happening with each sample.

When I hit reset collected results, several seconds later, I'm
immediately seeing several objects listed with an average age of
64,439.
Comment 1 iformanek 2005-09-19 18:12:03 UTC
This is strange, the generations should indeed reset to 0, and all testing I am 
performing does that correctly.

Is there something special about the app you are profiling? Can you send me a 
snapshot of the data right after the reset and/or specify the exact settings 
you use (e.g. copy'n'paste from the IDE log file)?

Is the generations number high for all classes or only for a small number of 
them?
Comment 2 iformanek 2005-10-21 17:41:26 UTC
I forgot, that I entered the issue myself, Jon, can you please add your 
comments here?
Comment 3 jchristi 2005-10-21 19:36:37 UTC
Until there is a new build available without the Access violations problems, I
wont be able to get things running under the profiler for one hour, let alone 50
hours :)
Comment 4 iformanek 2005-12-11 14:49:32 UTC
We will not address this in 1.0
Comment 5 J Bachorik 2006-09-13 12:03:41 UTC
Closing this issue as "works for me" for the current dev build.
If the problem persists, please, reopen the issue.