That's what i do right now. My app does its best to have as much
memory as possible before starting to open a big image for editing (i
have written a notification-system that caches and other classes can
register with. They'll then get notified when bitmap memory is
necessary, asking them to free as much 'bitmap memory' as possible
(and other memory if necessary)).

But if an OOM error still happens, i catch it, clearing even more
memory and putting up a Toast to warn the user something has gone
wrong and that he/she may try again.

This scheme works quite well, but my app would like to know if it
could open a full-sized image in 32-bit color or a if it should
present the user with the option to select full-size image with 16bit
color or a half-sized image in 32bit color. For now, i'm using this
hard-coded 6MByte as a limit for maximum image size.


On May 14, 12:00 am, Dianne Hackborn <[email protected]> wrote:
> You can always catch the exception.
>
> On Wed, May 13, 2009 at 4:59 PM, Todd <[email protected]> wrote:
>
> > So, how does one programatically determine the amount of heap space
> > free including space used by bitmap memory? Is there such a way? I
> > would prefer to inform my users that there isn't enough memory to load
> > their image rather than getting an OOM and have the app exit.
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to