OK, but not if you are a foreground app, wouldn't be very silent ;-)
> Pretty universally people coming from a desktop environment have a very
> different definition of "reasonable amount of memory" than is actually sane
> for a mobile environment.
I am talking sane for a mobile environment, and I already mmap
everything I can. Let's say an absolute max of 2 full 8mp images, so
about 64MB of extra space in native, is that reasonable for a
foreground app? Keeping in mind that it is the user's choice to do
this (just like he would play a high performance game)
On Jun 8, 11:56 pm, Dianne Hackborn <hack...@android.com> wrote:
> On Wed, Jun 8, 2011 at 1:15 PM, webmonkey <webmonke...@gmail.com> wrote:
> > How does the native heap actually tell you, will malloc return NULL if
> > it cannot reserve enough space?
>
> No, as I said, your app will eventually be silently killed.
>
> > And if you are a foreground app, you won't get in trouble will you
> > (unless you use insane amounts of it) I can understand that a
> > background app should not use more native memory than the limit.
>
> Pretty universally people coming from a desktop environment have a very
> different definition of "reasonable amount of memory" than is actually sane
> for a mobile environment.
>
> --
> Dianne Hackborn
> Android framework engineer
> hack...@android.com
>
> 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment