Closed Bug 865456 Opened 11 years ago Closed 11 years ago

Crashing and restoring is resuming with a blank session (apptabs are still restored)

Categories

(Firefox :: Session Restore, defect)

23 Branch
defect
Not set
critical

Tracking

()

RESOLVED INVALID
Tracking Status
firefox23 - ---

People

(Reporter: jaws, Assigned: ttaubert)

Details

(Keywords: dataloss)

I've had three crashes today and in all three instances all of my tabs were lost when I resumed (with the exception of the apptabs).

Some of these crashes are happening while scrolling and others happen when I switch tabs.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Regardless of what is the crash-of-the-day, we shouldn't be losing session state like this.

If the app tabs can be restored, then some of the session state isn't being corrupted. What's happening to the rest of the session?
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Severity: normal → critical
Keywords: dataloss
I don't know if this happened in 22, but it's certainly happening in 23.
Tim, can you take a look at this?
Assignee: nobody → ttaubert
Status: REOPENED → ASSIGNED
OS: Windows 7 → All
Hardware: x86_64 → All
I could reproduce this on my trunk build as well and then realized that 'browser.sessionstore.resume_from_crash' was set to 'false'. Jared and Joe had the pref flipped as well. I interestingly couldn't find any code that sets it to false, the default value is true.
We figured out this pref gets set to false when using the mozregression tool.
(In reply to Tim Taubert [:ttaubert] from comment #7)
> We figured out this pref gets set to false when using the mozregression tool.

So is there anything to do here other than know this pref gets set by the tool?  Should the toolmakers be asked to reset the pref at the end of a run?
Yeah, the tool should be fixed. Jared filed https://github.com/mozilla/mozregression/issues/66 though, so I don't see a need to track this here.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.