I rely a lot on Firefox's Session Restore feature. I have configured the browser to always open the last session when it gets opened and for the most part it works just as advertised.
While there are other methods to ensure that, like bookmarking tabs regularly before you close the browser, it is not really as comfortable of an option as the built-in session restore feature.
With that said, the Session Restore feature of Firefox is far from perfect. While it does a good job normally, I sometimes experienced issues in regards to that.
Sessions would not be loaded but the Firefox home page would. That's a big problem if you rely on the feature as you may not be able to recover all websites that were open during the last browsing session.
You can try and recover sessions, but that may not work all the time. Some users have helped themselves by using third-party add-ons instead like Session Manager which provides you with more control over the whole saving and restoring process.
Mozilla just announced that it has made improvements to Firefox's Session Restore feature that it plans to ship with Firefox 33.
The new feature attempts to minimize data loss in regards to sessions by improving how backups are stored and recovered again.
The new backup process
The restore files
As mentioned before, Firefox saves several new session restore files to the user profile directory once the new feature lands in the browser (Nightly users already have it as it lands in Firefox 33 if things go as planned).
The new process
Here is the order in which Firefox attempts to restore the previous session on start.
So what is different in comparison to the old session restore? First of all, you may notice that additional files are saved by the browser which increases the chance that one of the session restore files is not corrupt and working.
In addition, both the previous.js and upgrade.js files are not replaced as often as the two main session restore files. This provides another option of recovering a session if both primary session files are no longer working, or if you have started the browser several times after you noticed that the session was not restored properly.
The new system offers additional means to recover sessions manually as well. Previously you had to rely on the backup file only to restore a session if the main sessionrestore file was corrupt. Now, you can also try recovery.js or upgrade.js, both of which are usually created farther back in time making it more likely that they are not corrupt as well.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.