There's a bunch of discussions about this issue in this forum, just dig a little and you will find what you need to know. Also, Romain Guy posted a write-up about un-binding views (and bitmaps) from activities. http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html
Admittedly, a lot to read up on. On Jan 23, 3:48 am, ad <avra...@gmail.com> wrote: > I've problem with memory of the bitmaps, > I'm creating a lot of bitmaps and then releasing them by recycle() and > after many retries I get: > > java.lang.OutOfMemoryError: bitmap size exceeds VM budget > > How to get rid of this??? > The problem is that even if i close the activity (call onDestroy()), > in next program run the bitmap memory is still allocated!!!! (I've > also android:clearTaskOnLaunch="true" in my manifest). > This is horrible. Can anybody help me with that? > I suspect that every application using BitmapFactory.decodeResource > must get this exception in some call! > Do you have any idea what's going on? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
