> catch( Exception e )
> {
> System.gc();
> bm = BitmapFactory.decodeResource( resources, R.drawable.my_bm );
>
> }
>
> I know it's not the prettiest, but I've never seen the second attempt
> (after GC) fail.
Interesting. So, what you are saying is that Dalvik's GC does not a
good job freeing memory on its own?
I'll try if this work around makes it any better. However it is
limited because some of the Bitmaps get loaded during initialization
of layouts, where you can hardly interact. Hmm, a try/catch around
each setContentView also? Boy, this is getting ugly... ;)
--
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
