On Jan 25, 10:41 pm, William Ferguson <[email protected]> wrote: > Ie it only shows those allocation that are resident in memory at the > time you click on Get Allocations. So if anything has been GCed prior > to that its not visible.
It always shows the last (up to) 512 allocations. The GC has no effect on the allocation tracker. With the latest version of DDMS you can sort the list in various ways, including allocation order, so you can see what happened most/least recently. There is currently no way to increase the limit beyond 512, other than changing a constant in Dalvik and rebuilding the VM (see dalvik/vm/ AllocTracker.c, kNumAllocRecords). > I'm pretty certain I know where at least one main offender lies, but > I'd really like some emprical evidence that I'm hitting the right > target before I clean it up. If it's one of your classes, there are various ways to instrument the constructor so you can watch the allocations. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
