739595 - Session is not always restored after a Force Stop

Status: RESOLVED DUPLICATE of bug 735399

(Firefox for Android Graveyard :: General, defect)

Description

[Adrian Tamas (:AdrianT)]

Attachment: Logs while reproducing the issue

Fennec/14.0a1 2012-03-27
Device: Motorola Droid 2 (Android 2.3)

Steps to reproduce:
1. Create at least 3 different tabs.
2. Minimize Nightly using the Android Home button.
3. Open the App Manager and Force Stop Nightly.
4. Open Nightly again.

Expected results:
The session is restored.

Actual results:
7 out of 8 times the session was not restored.

Note:
The issue is not reproducible if Nightly is closed using the Advanced Task Manager.

Comment 1

[Mark Finkle (:mfinkle) (use needinfo?)]

Brian - Is a force-quit affected by the 30-second rule? Or is it handled like an OOM (always restore) ?

Comment 2

[Brian Nicholson (:bnicholson)]

(In reply to Mark Finkle (:mfinkle) from comment #1)
> Brian - Is a force-quit affected by the 30-second rule? Or is it handled
> like an OOM (always restore) ?

Yes, the two cases that the 30 second compromise were meant to handle were
1) force stop/task kills, and
2) crashing

Ideally, we actually *never* want to restore the session after the user has Force Stopped, and we *always* want to restore the session after a crash (excluding crash loops). I think this will be our final design, but we need bug 735399 to land first. The 30-second restore we have now is a compromise, whose rationale is discussed at https://bugzilla.mozilla.org/show_bug.cgi?id=718240#c18.

Note that the 30-second restore is based on the last time sessionstore.js was touched and not the moment Fennec is paused or killed.

Marking as a dupe of bug 735399 since that will remove the timeout and fix the inconsistent restore.