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.
Created attachment 24886 [details]
Allocation stack traces - results snapshot
Self assign for 1.0
Will not address in 1.0
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".
Reproduced in todays daily build.
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.