Closed Bug 1757249 Opened 2 years ago Closed 2 years ago

Although "Open previous windows and tabs" is deselected, previous windows and tabs are opened after unexpected termination or crash

Categories

(Firefox :: Session Restore, defect)

Firefox 96
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: squeevee, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0

Steps to reproduce:

Make sure the option Settings > General > "Open previous windows and tabs" is deselected.

Open some tabs and windows

Kill the Firefox process, i.e., pkill firefox

Reopen Firefox

Actual results:

All previous windows and tabs are restored

Expected results:

One window should have opened to a blank page (as that is my selected homepage setting)

I was able to reproduce this with both the Arch Linux package and the Flathub package builds of Firefox.

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Tabbed Browser

Hey qqueevee,
Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .
Testing with a fresh new profile could help. You can find more about creating a new profile here : https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile .
If possible, you can test this issue on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .

Flags: needinfo?(squeevee)

(In reply to Andrei Purice from comment #3)

Hey qqueevee,
Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .
Testing with a fresh new profile could help. You can find more about creating a new profile here : https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile .
If possible, you can test this issue on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .

There appears to have been an update since I reported the bug and I am getting slightly different results than I was previously. Instead of immediately opening previous windows and tabs, I am now getting a "We are having trouble restoring your session" page. I would still consider this to be unexpected behavior since I have explicitly specified in my settings that I do not want to restore previous windows and tabs on launch. (but I'll admit this case is a little more ambiguous)

This result happens regardless of whether I use --safe-mode or a fresh profile, in both the Arch Linux build (97.0.1) and in the FlatHub build (98.0)

I will test with the nightly build soon

Hello! I have tried to reproduce the issue with firefox 107.0a1(2022-10-10) with Ubuntu 22.04 but unfortunately I wasn't able to reproduce the issue I will set a component for it in order for our developers to take a look on it and provide a solution. If it's not the right component please feel free to change it to an appropriate one.

Component: Tabbed Browser → Session Restore

Redirect a needinfo that is pending on an inactive user to the triage owner.
:dao, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(squeevee) → needinfo?(dao+bmo)

(In reply to squeevee from comment #0)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0

Steps to reproduce:

Make sure the option Settings > General > "Open previous windows and tabs" is deselected.

This is meant for the user intentionally quitting and restarting Firefox. Crashes often disrupt what the user may be doing so we intentionally make an exception there. I realize that this also affects users who quit Firefox by killing the process, but from what I know, we can't really tell intentional killings and crashes apart. So these users should probably adjust there workflow to avoid these kind of problems.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(dao+bmo)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.