On Wed, Sep 9, 2009 at 9:19 AM, Peter Jeffe <[email protected]> wrote:
> 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. > Of course it can grow the heap. It will also use mmap for allocations over 64K so they aren't in the main heap at all. (Fwiw, the allocator is a somewhat modified version of the standard dlmalloc.) > 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. > The standard maps app uses the same library, and at this point doesn't have such problems as far as I know. My guess is that put together your app is just using too much memory. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
