On Aug 28, 3:17 pm, fadden <fad...@android.com> wrote: > The bitmap memory isn't actually stored on the VM heap -- it's an > "external allocation" -- so improvements to the GC will not help this > much.
I assumed that the problem is that the native code tries to allocate memory but the native allocator for some reason can't move the heap boundary--basically it seems like Android's malloc() doesn't just call brk() or its equivalent when it needs more memory, so it rejects the malloc instead. To me this is a critical problem. We have a map-based app that gets frequent errors when the map framework tries to allocate new images to draw the screen. We have absolutely no control over their code, can't retry allocations etc., so our app just dies. This is a very serious problem, has been since the start of Android, and really needs to be fixed. In my own code I can catch the OOM error and free up memory, do gc() calls, and retry, and that usually gets me past it, but I have no such options when other code is doing the allocation. Is there a reason why this isn't considered a serious problem that should be fixed ASAP? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
