527171 - session restore does not function unless you shut it down thru start menu

Status: RESOLVED WORKSFORME

(Firefox :: Session Restore, defect)

Description

[wcarroll]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)

session restore does not function unless you shut it down thru start menu. If using the x in top right, if it crashes, if i experience a power outage, session restore does not work ... on re opening, i get my google homepage and i start remembering to replace 

Reproducible: Always

Steps to Reproduce:
1.close a session with session restore checked via the x in top right
2.session closes
3.try to restart ... it will restart to google homepage, not to previous session.
Actual Results:  
session did not restore

Expected Results:  
the session with all/any tabs should have been restored

SUGGESTION: MAKE SESSION RESTORE PERMANENT WITH EVERY CLOSURE. HAVE A CHECKBOX MARKED "DO NOT RESTORE SESSION". IF U CHECK THE BOX, THAT WOULD BE THE ONLY TIME A SESSION WOULD NOT RESTORE.

Comment 1

[Daniel Veditz [:dveditz]]

Something is broken for you, you may need to get help through the http://support.mozilla.com/ forums.

By default, if you close a window with multiple tabs Firefox should ask you if you really wanted to close them all. If you close the very last window with multiple tabs then it should ask if you want to start with the same set of tabs next time (and then do so, of course). This last one is basically the feature you asked for in your suggestion at the end.

If you _crash_ you should definitely get your session restored -- that is the primary function of the session restore feature.

You should also be able to go into options and change your "homepage" to start up with the tabs that were open last time (assuming you exit from the file menu rather than closing each tab individually until you've closed them all).

If you NEVER got your session restored my first guess would be that your sessionrestore.js file is corrupt or read-only and that we failed to save the session info. But it sounds like you get the right behavior in one small case so that tends to throw out that theory. There are hidden preferences that can turn off the feature that maybe got changed accidentally, but that theory, too, is disproved by your "start menu" shutdown saving the tab state (I assume you mean the windows start menu, and powering down your computer).

Like I said, http://support.mozilla.com is your best bet for help on this.

Comment 2

[wcarroll]

If I try to exit thru file menu even with session restore checked, i never get a session restored on restart. the ONLY time i get a restart on a regular basis is when i check session restore under "tools" ... this has happened thru two updates ... I now have 3.5.5 as i received an update tonight. Yes, i checked and same problem exists

Comment 3

[Andrew Allison]

I have just the opposite problem, i.e., if I shut down from the Start Menu with more than one tab open, I consistently get the "This is embarrassing" error message when I restart. 
It could be an interaction with Avast, which always looks for, and if available installs,any update(s) on startup, commandeering the system until it's done. This is, of course a good thing: you'd like to have the very latest database before going on-line, but it may be confusing Firefox.

Comment 4

[Andrew Allison]

Additional information: The reporter of the author of the bug specified reports that it was fixed. The problem which I report above (and will enter separately) is that if Firefox is closed by the OS (as in Start/Turn Off Computer/Turnoff) with more than one tab open and Options set to Start at Home Page, it tries (and fails) to restore the previous session. Selecting "restore" in Options and closing just Firefox results in the session being saved and restored.

Comment 5

[Wayne Mery (:wsmwk)]

(In reply to comment #4)
> Additional information: The reporter of the author of the bug specified reports
> that it was fixed. 

wcarroll, what changed to cause it to work?  Or if you don't know, then _when_ did it start working?