It is also interesting to notice: according to the official documentation for Android Java at developer.android.com, System.gc() is only a hint; it is no guarantee that garbage collection will actually take place.
That said, people have told me that the hint is usually taken. On Feb 25, 3:07 pm, String <[email protected]> wrote: > Sounds to me like you are probably hitting the bitmap deallocation > problem:http://code.google.com/p/android/issues/detail?id=8488 > > In summary, the issue is that bitmap memory takes several GC passes to > deallocate, so it's really easy to get ahead of the GC and run out of memory. > > AFAIK, there's no fix. You can help the situation somewhat by calling > System.gc() after every Bitmap.recycle() call, and again before every bitmap > allocation. But that's only somewhat. I've also found that setting bitmap > variables to null after recycling them makes matters worse, but YMMV. > > 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
