my app has a main activity with a list in it which then launches activities on it in response to pokes at the list. each list item has two Bitmaps associated with it, one small and one potentially large (~1mb). pokes at the graphic flip which Bitmap gets shown.
after the user pokes too many and i get an OOM exception, i flip the views back to the small version, recycle() big bitmaps, retry, etc. also i recycle() when the views get put in the recycle bin, when the activity gets paused, all that. i'm trying to be good here. but i'm seeing situations where even though all of this has happened, and in theory all the "big" bitmaps are recycle()d etc, the app is still out of memory and can't do anything. are there subtleties to the bitmap.recycle() strategy as a way of handling low memory situations? thanks -- jason.vp.engineering.particle --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
