Firefox offering to restore previous sessions even after clearing cache
As a web designer it's important for me to be able to clear all the cache in my browser so I know I am getting content directly off the server and nothing is out of date. Firefox has enabled me to do, and I have set it's default behaviour up to clear everything on exit. That way I can just close the browser and know when I re-open it it's all ready.
The privacy nut part of me doesn't want my browser remembering anything between sessions, I am able to remember my passwords and usernames, as well as being able to fill in data perfectly fine so I don't need anything being remembered. History is another thing, if I want to go back to something I will add to the read later or as a favourite, I don't need the history after I close the session. Again I have been able to achieve this with Firefox's privacy settings.
After saying all this, it is also important to me that while ever I have a Firefox session open, my history, pre-filled data, cache, etc. are all available to me. Again, Firefox has allowed me to do this. It is also important that if Firefox crashes, and as a web designer I make this happen quite frequently :D, I want Firefox to offer to restore my previous sessions, yet again Firefox could do this.
Now here comes the problem. As of a few months ago I have noticed an intermittent problem with it offering to restore the previous sessions. When I say intermittent I mean it will offer it for days and weeks at a time, then stop and then start again. Now I haven't kept a track of updates and can't tell you if it's coming and going with updates, but I can tell you that the problem is present in the full release 45.0.1 but not present in the developer edition 45.0a2.
The settings in both versions of the browser are:
* Use custom settings for history * Always use private browsing mode - off * Remember my browsing and download history - on * Remember search and for history - on * Accept cookies from sites - on * Accept third-party cookies - always * Keep until - I close Firefox * Clear history when Firefox closes - on
Settings for clearing history
* Browsing and Download History - on * Active Logins - on * Form and Search History - on * Cookies - on * Cache - on * Site preferences - on (currently) * Offline Web Site Data - on (currently)
But yet, even with all that set whenever I close the browsers (every session) I can restore my previous sessions. I have watched task manager and have seen firefox.exe disappear, so I know it's closing. I have even disabled the setting for Firefox to restore tabs on a crash recovery, but it still does it (I was thinking maybe Firefox was exiting and had crashed instead).
This has been fine for years and years, but recently it's started happening. I have noticed this on several computers I use, all with different levels of customisation and add-ons, but all with the same settings.
Any ideas?
Isisombululo esikhethiwe
Just wanted to let you know that I received a FF update last week and I noticed it fixed the "restore previous session" problem. It now closes and opens like it should.
Also, the DE of FF "fixed itself". One day there was an update and it's not looked back since, in fact I am now on the update from last night.
And the fix was? For me at least, do nothing.
Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0All Replies (7)
The previous sessions open tabs are stored as part of the profile so they are available for Firefox to use if necessary. They are not part of the cache files or History database. They were recently improved
Possibly what you are experiencing is one of a maze of related bugs that have affected recent Firefox versions relating to shutdown and startup. At least some of those are or were occurring when History is cleared at shutdown.
Ideally changes are introduced in Nightly (Alphas) and stabilised in the Developer Edition (DE, nee Aurora) and Beta before going in to the Release. In practice things are more complicated as some fixes are considered more important and get pushed in higher up, even direct in to point Releases like 45.0.1 . Needless to say some fixes could have unforseen consequences.
If you see a bug on a Current release like Fx45.0.1 it is good policy then to test the latest Nightly, currently Fx48.0a1 (They will have daily builds ) If your are using DE you should also only try the latest version and build: currently Fx47.0a2 rather than the outdated Fx45.0a2
If you see no problem in Nightly the bug is hopefully already fixed and will work its way through to the Release.
If not, and you are unable to see a bug filed then please file one yourself with Step To Reproduce (STR). (We are glad to assist if need be, but as a developer yourself you are unlikely to need help.)
Note if you do see a reproducible bug and you have simple and quick STR you should even be able to pin down the exact regression point. If you are able to do that the Firefox developers are likely to respond sooner as it will be clear it is valid regression needing fixing. There is a handy tool mozregression as explained and available here http://mozilla.github.io/mozregression/
Some of the possibly related bugs 871908, 1248489, 1248837
- Kindly also note bugzilla etiquette Please think carefully about posting in other people's bugs. Although me too type comments are not wanted, sometimes there are requests for information and examples.
- Bug 1248837 - shutdownhang in nsThread::Shutdown() | Firefox crashes, sometimes the restart fails
- (Mainly fixed in Fx45} Bug 1248489 - crash in mozalloc_abort | NS_DebugBreak | nsDebugImpl::Abort (with abort message chrome://browser/content/sanitize.js) and Firefox no longer responding on startup
- Bug 871908 - Clearing "browsing and download" history does excessive disc IO (due to huge wal file)
Thank you for the response.
I thought I was on the current Developer Edition as it says it's up to date.
I have only started using it recently to get a bit of a heads up on potential problems with Firefox in a work environment, so I haven't really noticed it's out of date. Should I just get a fresh copy off the site or should it be updating?
Regarding working through the nightly's for the normal release, will I have problems rolling back? I have lots of different development tools installed on my work system, so I will probably try it on my cleaner home one.
Thanks again.
There may have been issues with the update server see . We are also aware there is malware around that blocks updates. By default all Firefox installs including prereleases update automatically.
You should be using multiple profiles.
If you run multiple instances of Firefox at the same time note to use -no-remote on the launch of additional profiles and versions but not on your default profile and version.
DE does now install by default as a separate browser with it own profile. Not sure about Nightly. I usually setup multiple profiles and multiple installs anyhow.
As for testing for regression ranges the mozregression tool, from what I remember, uses a separate install directory and I think a virtual or temporary profile, anyhow that will not interfere with your other installs. It handles the install, uninstall & startup process for you once you pick the range to bisect.
Thank you, I will take a look into it.
I will add, the DE did update today, but only to 45.0a2 (2015-12-23) and says it's up to date.
I am currently on 47.0a2 (2016-03-26) there may have been server issues or no updates over a weekend but totally different from yours.
It may be worth doing malware scans with the all the tools recommended in
Also look for hidden addons. Pocket and whatever Hello uses may be expected, others may be suspicious. Of course check in each profiles that you have not set Firefox not to update !
Isisombululo Esikhethiwe
Just wanted to let you know that I received a FF update last week and I noticed it fixed the "restore previous session" problem. It now closes and opens like it should.
Also, the DE of FF "fixed itself". One day there was an update and it's not looked back since, in fact I am now on the update from last night.
And the fix was? For me at least, do nothing.