Monday, September 26, 2011

[android-developers] Re: Activities aren't getting killed by ActivityManager when app is running out of memory

Hi SOB,

No, since according to the SDK docs, that function is supposed to run
on general OS low memory and not on application low memory. On a real
system, these will almost never coincide, unless my app happens to
overflow the OS to a low memory state.
http://developer.android.com/reference/android/app/Application.html#onLowMemory%28%29

However, I do get this in the log every time: INFO/
ActivityManager(61): Low Memory: No more background processes

This is kind of confusing, because the emulator shouldn't run out of
memory just because my app is getting close to its heap limit. These
are the kinds of things I'm confused about and looking to clarify
here.

On Sep 26, 3:36 pm, Streets Of Boston <flyingdutc...@gmail.com> wrote:
> Just for debugging purposes:
> Have you implemented the Activity's method 'onLowMemory()'  and put a
> debug/logcat statement in there to see it this one gets called or not?

--
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