Open Bug 646146 Opened 12 years ago Updated 6 months ago

Session restore activates occasionally after a normal close, with browser.sessionstore_resume_session_once is set to false


(Firefox :: Session Restore, defect)

4.0 Branch





(Reporter: johnsc301, Unassigned)


(Whiteboard: [bugday-20110401])

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20100101 Firefox/4.0

With multiple tabs open, sometimes when firefox is closed normally it will restore the previous session when opened again. This could be because firefox hangs slightly before close on Ubuntu. When I click close on firefox 3.6 or firefox 4, the browser takes a few sections to close and a few more for the firefox-bin process to end, sometimes resulting in an error message that another firefox process is open.

Reproducible: Sometimes

Steps to Reproduce: multiple tabs
Actual Results:  
occasional session restore upon normal closing.

Expected Results:  
session restore should never activate on a normal close.
Does this only happen at times when you see the "Another Firefox process is running" error? Also, what are your session restore settings?

browser.sessionsotre__resume_from_crash is set to true.
browser.sessionstore_resume_session_once is set to false
I do not get the another firefox process error. I recently did an uninstallation and reinstallation of firefox (reinstalled after deleting ~.mozilla folder).
I think the firefox 4 installation on Kubuntu 10.10 is screwy because no official source was given to 10.10 users. The only option we have is to download the source from kubuntu 11.04
I'll make sure it's all good when I do a clean install of kubuntu 11.04
For sake of testing, can you try to reproduce this in GNOME too? Officially we only support & test Firefox on GNOME. If this bug is unique to KDE, it's most likely a WONTFIX.
Whiteboard: [bugday-20110401]
Mozilla/5.0 (X11; Linux i686; rv:2.2a1pre) Gecko/20110407 Firefox/4.2a1pre

I must say that I've seen this issue also on WinXP, but I cannot provide STR's as it is not always reproducible. 

It happened to me when closing my computer with the Shutdown function in Windows, without closing Firefox first.
Mainly logging out and shutting down with a ff window open has given me this issue.
Sometimes when the OS is shutting down with Firefox still open, the Firefox process doesn't actually go through the full shutdown process and so it thinks it crashed. So we restore the session next time around.
Version: unspecified → 4.0 Branch
I am able to reproduce this bug easily, and I've found a way to produce it every time:


When Firefox Starts: Show a Blank Page
Always Show the Tab Bar:  Yes
browser.sessionstore.enable:  true  (although works the same when false)
browser.sessionstore.resume_from_crash:  false
browser.sessionstore.resume_session_once:  false

Since I have the Tab bar always visible, I can choose to exit Firefox in two ways:

1.  Press the Close button in the Windows title bar (same as Alt-F4 or File / Exit)
2.  Press the Close button on the tab bar, to close the last tab (same as Ctrl-W).

It matters which method I use to close Firefox!

If I close the window using File / Exit or via Alt-F4 or by closing the browser window, the next time I start up Firefox, it will restore whatever page was visible.  It will do this regardless of whether sessionstore is enabled or not!

If I instead close the window using Ctrl-W or by clicking the close button in the tab bar, the next time I start Firefox, it will obey my startup setting and open with a Blank Page.

This behavior is new, and seemed to show up in the very latest updates of 3.6, and the behavior has persisted after upgrading to 4.0.
Paul, is there any feedback you can give me on your expectation for comment 7? Seems to me like File/Exit and ALT+F4 should behave the same as CTRL+W.
Summary: Session restore activates occasionally after a normal close. → Session restore activates occasionally after a normal close, with browser.sessionstore_resume_session_once is set to false
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.