On Sep 10, 5:54 pm, Peter Jeffe <[email protected]> wrote:
> 09-11 00:45:00 .maps(649) softlim=13120KB, extlim=7232KB,
> extalloc=7232KB
>   freed 1136 objects / 115712 bytes in 84ms
> 09-11 00:45:01 .maps(649) softlim=13568KB, extlim=8128KB,
> extalloc=8128KB
>   freed 3920 objects / 954368 bytes in 94ms

This isn't entirely making sense to me, but it's possible we're not
seeing something.  At the least it's saying you've got 7-8MB of
external allocations, presumably for the map tiles.  (I think there's
1MB of common resources that the "zygote" grabs before you begin.)

A soft limit of 13MB means the heap was pushed out that far at some
point (remember, the actual extalloc computation is vs. the footprint
size, which sadly isn't displayed).  If it's stuck out there due to
fragmentation, dlmalloc's notion of the footprint size could be
smaller than that.  The part that's a bit confusing for me is that it
appears to push the soft limit out, which it would only do if
something didn't fit anywhere in the heap (again, possible for a large
object when there's lots of fragmentation).

(At one point we had a graphical heap display in DDMS, but it's been
disabled since launch and seemed a little broken the last time I
fiddled with it.  Was useful for looking at fragmentation.)

Can you crank up the verbosity in the script (debug=True in
handleGcInfo)?  That'll show among other things the current bytes
allocated, which might be revealing.  If the total size of all objects
is much less than the soft limit, *and* dlmalloc is ignoring the
fragmented areas during the footprint size calculation, then these
numbers might make sense.

At any rate, this raises questions: (1) how did the soft limit get
that high?  (2) why is there 7MB of stuff in the external alloc area?

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to