Thank you for the links to the bug reports. Until now I didn't discover the situation that "old" bitmap memory is lost. Anyway, I will check the workarounds.
On 17 Nov., 09:28, String <[email protected]> wrote: > On Nov 16, 8:31 pm, manayv <[email protected]> wrote: > > > I learned from several discussions of this group that > > BitmapFactory.decodeFile() allocates heap memory outside of the "java > > heap". > > Not only that, but the external-memory implementation appears to be > buggy. It's very easy for "old" bitmap memory to be unavailable for > GC, even if you're doing everything by the book. See these bug reports > (among > others):http://code.google.com/p/android/issues/detail?id=9897http://code.google.com/p/android/issues/detail?id=8399 > > So if you're doing more than one BitmapFactory.decodeFile() - or > creating sizable bitmaps any other way - some of your external memory > may be going there. Tips to work around the problem can be found in > those bug reports. > > HTH, > > 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
