Firefox 56, unlike 55 and prior, annoyingly tries to "Restore Session" upon opening a new session
On two Windows 7 pc's, the update from Firefox 55 to 56 resulted in the new, near-continual annoyance of new Firefox sessions opening with a "Restore Session - Well, This is embarrassing" tab, the session referred to often being simply my home page (duckduckgo). And this even occurs after running both Clear All History (range: Everything, details: All checked), and CCleaner (All checked).
I'd like a new session to open on my homepage, and not this new Restore Session nonsense.
On the two up-to-date pc's, Firefox updated days apart based on ongoing sessions (all closed without errors), and with the above History and CCleaner actions taken afterward. Logically this is a flaw in Firefox 56, which I hope is resolved.
If Firefox developers are listening, thank you for your time.
Alle Antworten (3)
This suggestion is based on other threads, so apologies if it's not the explanation:
If you use CCleaner, you can go into its settings and deselect the option to clear your Firefox session data.
Firefox 56 changed the format and name of the session history files, and this may be causing this new incompatibility issue.
Geändert am von jscher2000 - Support Volunteer
For anyone interested, for the time being I have set all about:config "sessionstore" Boolean operators to false, and this has resolved the issue.
Furthermore, the History - Restore Previous Session menu option still seems to be working OK, after a couple of minor tests.
Given the complexities of browser settings these days, it would be nice if Firefox updates carried over any particular user's about:config settings after an update. Instead it appears they are all reset. Such a nicety is desirable since the options under Options fall short of meeting user needs, in my view.
makaio said
Given the complexities of browser settings these days, it would be nice if Firefox updates carried over any particular user's about:config settings after an update. Instead it appears they are all reset.
Having all preferences reset during an update is not normal. There may have been a glitch during your update that caused a Refresh, or a file lock or corruption issue affecting the prefs.js file.