Thanks for these tips. At 1:14 PM -0700 4/30/09, Streets Of Boston wrote: >In my app, i've been dillegently 'unloading' bitmaps when i need >memory. >- clear any bitmap cache
I assume you mean any of my own bitmap caches... >So far, this scheme has served me well. Before i got a lot of OOM- >errors. Now i get a looooot less. And, if i still get one, i try to >handle it gracefully. It still seems like Voodo to me. If I have to manually call setImageBitmap(null) it implies (to me) that the image view is not being released in the first place, which means the view hierarchy is not being released, even though I have called finish(). At the moment I am looking for static variables and leaked contexts.... -- Ward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
