I'm sorry, I've certainly misunderstood something then, but... while coding an app dealing with bitmaps, this is what it looks like. Reading posts and blogs about memory management and use of bitmap led me to that conclusion, and carefully recycling bitmaps in my app allowed me to get rid of a lot of memory allocation exceptions.
Anyway, about memory leaks on orientation changes, another blog post from Romain Guy could be useful: http://www.curious-creature.org/2008/12/18/avoid-memory-leaks-on-android/ You might try this Drawable.setCallback(null) trick... On 17 août, 22:02, Marco Nelissen <[email protected]> wrote: > On Mon, Aug 17, 2009 at 7:53 AM, Nivek<[email protected]> wrote: > > > When you change the device orientation, you app is closed and then > > reopened. > > > Android handles bitmaps a "special" way, you HAVE to explicitly > > recycle them as soon as you don't need them anymore... or they stay > > allocated in memory and NEVER get freed. > > That is not true. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
