Re: [android-developers] Multitasking on Android - Why So Incredibly Bad?

Frank Weiss wrote:
> I think the OP's issue is that the Andorid Browser doesn't save the open
> windows state upon close (force close in the OP's case).

The Browser rarely goes through a normal close, because Browser uses the
BACK button for browser operations, so eventually people just start
using the HOME key rather than BACK their way to the beginning.

BrowserActivity does have an onSaveInstanceState() implementation and
uses it. Apparently, when a device is low on some memory resource, with
a Browser with a lot of windows open, the Browser process gets
terminated without going through the normal activity-destroy operation.

> I've confirmed
> this with just a reboot - but that may be a different syndrome.

Nothing saves its state after a reboot, at least in the same
"state-saving" that it would after being kicked out of RAM. That state
is held in RAM itself and is not persisted AFAIK.

--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Warescription: Three Android Books, Plus Updates, One Low Price!

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