On Nov 8, 6:39 pm, Kumar Bibek <[email protected]> wrote: > Try creating a Bitmap with smalled dimensions.
Good advice, as far as it goes, but sometimes you do need larger bitmaps. :^) One obvious optimization: do you really need ARGB_8888? Perhaps you do, but if not, other Configs take half the RAM or less. The other thing you need to be aware of, IMHO... there's a platform bug in deallocating bitmap memory. See http://code.google.com/p/android/issues/detail?id=9897. If you're doing repeated bitmap creation, you're likely to be running into it. Easiest way I know to work around it is to ensure you use Bitmap.recycle() when you're done with each one; do NOT set your bitmap variables to null. Good luck with it! String -- 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
