Bug 64550 - In some cases the allocation stack traces object count does not precisely match number of objects reported in the allocation results
In some cases the allocation stack traces object count does not precisely mat...
Status: NEW
Product: profiler
Classification: Unclassified
Component: Base
5.x
All All
: P3 (vote)
: 7.2
Assigned To: Tomas Hurka
issues@profiler
: VISUALVM
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-16 16:16 UTC by iformanek
Modified: 2011-11-02 20:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments
Allocation stack traces - results snapshot (27.33 KB, application/octet-stream)
2005-09-16 16:17 UTC, iformanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-09-16 16:16:44 UTC
In some cases the allocation stack traces object count does not precisely match 
number of objects reported in the allocation results.

Example is attached memory snapshot - the char[] has 532 objects allocated, but 
the Allocation stack traces root only reports 531.
Comment 1 iformanek 2005-09-16 16:17:23 UTC
Created attachment 24886 [details]
Allocation stack traces - results snapshot
Comment 2 iformanek 2005-09-16 16:17:48 UTC
Self assign for 1.0
Comment 3 iformanek 2005-12-11 13:48:15 UTC
Will not address in 1.0
Comment 4 Maros Sandor 2006-01-24 11:30:05 UTC
I have also experienced this. I am allocating 17 objects and selected to track
evety 10th allocation stack trace. In the Allocation Stack Traces view in the
Objects Allocated column there are two issues: 

1) it is not consistent ... it sometimes shows 2 and sometimes 3
2) both values are wrong and the value should be 17 (we know this count precisely)

There is another minor issue associated with this: the UI for setting this up is
misleading. Track Every XXX allocations text field should be only enabled if the
Record Stack Traces checkbox is checked. It should also be renamed to something
like "Record Every XXX stack traces".
Comment 5 Tomas Hurka 2007-09-11 09:05:23 UTC
Reproduced in todays daily build.
Comment 6 Tomas Hurka 2007-09-11 11:50:56 UTC
The root cause is that number of allocated objects is tracked separately and for take snapshot - number of allocated objects is obtained in different time than 
other informations like object sizes and stacktraces. It will not be fixed in 6.0.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo