Closed Bug 1626731 Opened 6 years ago Closed 5 years ago

Firefox doesn't open all windows when restarting

Categories

(Firefox :: Session Restore, defect, P3)

Product:
Firefox
Component:
Session Restore
Version:
74 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INACTIVE

People

(Reporter: tim.koers, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

(Keywords: dataloss, steps-wanted)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

I closed Firefox using the taskbar -> Close option.

Actual results:

I had 4 windows open with loads of tabs and one window (my main window) with 40+ tabs is missing.

Expected results:

All the windows should have opened correclty.

I hope that you can fix this really soon, since I'm really pissed of by this.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Session Restore

I have never seen this happening with usually about 20 tabs open, so this will require clearer and more specific conditions which allow someone else to reproduce this.

This is happening right before my computer reboots or shutsdown, but also when using the taskbar to close them. The windows where located in different Desktop environments (Windows Flag + Tab) but I moved them to my main Desktop environment prior to closing Firefox. I
My computer (and thus Firefox) was running for about 5 days straight.
I hope that I've provided some details about the conditions.

Observation:
I have been using Nightly for some time and at the very least I restart it once every day...sometimes even twice as and when I notice an update ready to be applied.

Right before the very last update when I thought of also logging back here and writing about the issue, I observed the very same issue as the reporter here mentioned. In comparison, I had two windows and after restarting the browser (with a gap of say 6-7 hours between quit and start), the main window which had tabs from much far back in history in Pinned tabs just didn't come back whereas an auxialliary window where i pushed out 3 tabs for later reading got restored fine. As I mentioned, that there was an update soon after. I had tried opening back another window now to load back the old tabs as much as i could remember. this time even with 2 windows and the restart for updating the browser, the correct number of windows opened.

Other things to know: I use Firefox (from mozilla's OBS repo on opensuse tumbleweed) alongside Firefox Nightly. I usually never quit either or turn off my PC. I had many tabs, like the reporter mentioned, (i kinda forgot how to tag names in bugzilla) in the main Nightly window but they were closed a day before when I sent them to my mobile device for later reading.

wait, so given that this is observed in Nightly, should I make a new bug or how will this be marked for Nightly as well.

I have experienced the same problem recently. I believe it started with version 74.0.1, though it could have been 74. I am something of a tab hoarder, keeping windows of tabs for various projects open when a new project interrupts them. My daily workflow is to Exit Firefox at the end of the day, watching for all Firefox processes to end before Shutting Down Windows 10. Lately, I have noticed that same windows haven't been present the next day when I reopen Firefox. I cannot discern any clear pattern to which windows have failed to restore - some were ones I had not touched for weeks, while others were ones that I look at several times per week. Nor can I say whether windows have disappeared one each restart, or if they have disappeared in batches. I do not believe any windows have lost individual tabs; rather it is a whole window that disappears.

The priority flag is not set for this bug.
:mikedeboer, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mdeboer)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Severity: normal → --
Blocks: ss-reliability
Severity: -- → S2
Flags: needinfo?(mdeboer)
Keywords: dataloss, steps-wanted
Priority: -- → P3

S1 or S2 bugs needs an assignee - could you find someone for this bug?

Flags: needinfo?(mdeboer)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.