Hello,

I'm experiencing an unexpected OS behaviour; mentioned at least on Android 
2.x, possible applicable to newer versions too.

When OS calls 
onSaveInstanceState<http://developer.android.com/reference/android/app/Activity.html#onSaveInstanceState(android.os.Bundle)>(for
 whatever reason) apparently application may be killed while within 
this call if it is run for rather a long time (several seconds).

Is there a known time limit for this call to run inside application?
Is this a proper behaviour in general?  It is not mentioned in 
documentation.
Is this preventable?


BTW, there's something ambiguous mentioned in 
onPause<http://developer.android.com/reference/android/app/Activity.html#onPause()>
 method:

> When activity B is launched in front of activity A, this callback will be 
> invoked on A. B will not be created until A's onPause() returns, so be sure 
> to not do anything lengthy here.

*Lengthy* is not a measurable thing :)


TIA.
Andrew.

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