Yes, the OOM is related to 'external allocations'. I googled
'dalvikvm external allocation' and there's plenty to pore over. Is
there an update on this issue in general?
Here's the relevant logcat excerpt:
01-21 13:04:49.140: INFO/WindowManager(79): onOrientationChanged,
rotation changed to 1
01-21 13:04:49.140: INFO/WindowManager(79): Setting rotation to 1,
animFlags=0
01-21 13:04:49.150: INFO/WindowManager(79): Config changed:
{ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3 orien=2
layout=18}
01-21 13:04:49.370: DEBUG/StatusBar(79): updateResources
01-21 13:04:49.680: DEBUG/dalvikvm(2630): GC freed 556 objects / 24056
bytes in 127ms
01-21 13:04:49.790: ERROR/dalvikvm-heap(2630): 614400-byte external
allocation too large for this process.
01-21 13:04:49.790: ERROR/(2630): VM won't let us allocate 614400
bytes
On Jan 21, 2:47 pm, fadden <[email protected]> wrote:
> On Jan 21, 12:58 pm, OldSkoolMark <[email protected]> wrote:
>
> > Is this telling me something useful? If forcing a GC with DDMS
> > reclaims the memory used by now-defunct instances of my activity, I
> > would have thought the VM would have garbage collected some, if not
> > all of these defunct activities automatically. Do I need to request GC
> > at the very beginning of my activity lifecycle to make sure?
>
> Something doesn't sound right. What does logcat show? Are you seeing
> GCs in the log file? Is the OOM related to "external 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
