Thanks for your interest in my problem. I read (and reread) that blog article early on and took its recommendations to heart. The possibility that I still have activity lifecycle bugs is of course real, but I've scrubbed it pretty clean with the Memory Analyzer and Allocation Tracker. One thing I observe from reading the threads found by googling, is that mishandling large bitmaps can cause this error under conditions I'm not real clear on. I'm using pngs for the background and two image buttons. Presently, I'm not doing anything special during onDestroy to free these images up. Should I be?
On Jan 22, 12:52 pm, fadden <fad...@android.com> wrote: > On Jan 21, 3:17 pm, OldSkoolMark <m...@sublimeslime.com> wrote: > > > 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? > > If it's happening after orientation changes, there's a good chance > it's a memory leak in your application. What I don't understand is > why a manual GC would change the outcome. > > Take a look at: > http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
