This doesn't save the page state, so if you were filling in a form, you'll lose that information, but it does mean that wherever you reopen Firefox, you end up pretty much exactly where you were when you closed it.
I guess you'd still need to regularly close and reopen the browser as a whole (I do that at end of the day anyway when I turn my machine off), but it may be more convenient than losing state.
Having to wait half a minute on every tab switch to wait for that gigantic mess of enterprise grade websites served from an ancient box on the other side of the solar system to load is not conductive towards concentrated work.
When I lose firefox (usually when power outage) I just cycle through all the tabs with ctrl+tab, by the time I get back to the first one it has reloaded (and the others do so in the background). It's not a big deal.
I lived through the days where force closing Firefox was the only way to preserve sessions. Things honestly aren't that much better. I'd take a zero percent chance of success over 80. At least then failure is known and predictable instead of just reliable enough to get you to trust it.
Opening a second window with CMD+N (mac user just like the sibling) often brings up some random page from my history. This has been so annoying that I disabled the restore feature. Since then I think it hasn't happened again.
(I now use Sidebery.)
Currently, the problem might be gone, I will try that out. Thanks for your answer!
Edit: I also don't have these stability issues, but I did have issues with my suspend mode on that laptop, no matter the os (win/ubuntu)
Maybe you should check it for suspicious DLLs using Process Exporer or outright attach a debugger and see what the UI thread is blocked on when it stops responding.
Plus, there's a delay of up to 2 minutes at launch, when Firefox reads something from disk for minutes, with minimal compute.
Bug reports on this result in denial.
It was quite visible in top or about:memory or about:processes
So maybe there's a real issue but us linux users simply aren't noticing it..
Another thought. Perhaps it is the sqlite db? Maybe a large one that somehow isn't getting vacuumed on shutdown?
Maybe try testing in a clean profile...
Edding for something more neutral: https://github.com/graysky2/profile-sync-daemon
I leave multiple tabs open for weeks+ on Windows (and android), I have never experienced any issue (except when windows decides to update - but firefox always restores itself without issue, or I can press ctrl+shift+t to reopen previous tab/session). There must be something specific to the other commenter's setup, whether it be specific addons or specific pages that are causing the crash.
I feel like I'm from another planet when I've been raised with the concept of "a reboot a day keeps the blue screen away".
I always shut it down on Friday evenings though.
You can use “Open previous Windows and tabs” to keep your tabs between restarts. It only works on the last window you have closed though.
Unless I say so, a normal web page shouldn't eat gigs of RAM or tons of CPU.
https://support.mozilla.org/en-US/kb/task-manager-tabs-or-ex...
Alt+F, Q exits all windows at once and also restores them the next time you launch firefox.
It's strange that it wouldn't report this as a crash. They're normally pretty good at telemetry (sometimes to a fault..)
General
Startup
[X] Open previous windows and tabs
In my case I like to be able startup the browser without opening all the prior tabs, but then be able to selectively reopen the prior tabs by window or by individual tab. That's what session managers do.
> They also suggest using their session restore feature after a hang, but with this type of crash, Firefox is never able to restore your tabs. It also doesn't record the crash report in about:crashes
Also the setting you suggested doesn't work if you have multiple windows that close. It only saves one window session.
?? It does? I have like 20 windows on the go with multiple tabs each and it brings them all back.
There's people in this thread repeating claims that are literally not true.
I know it's just paper over the real problem, but couldn't you restart at the end of the day rather than at the beginning?
It only ever lasts 3-4 weeks because Windows has to reboot for patches at least once a month.
You probably one of those people who confuse tabs with bookmarks and think you should have 500 tabs open with only 4 gigs ram and having not shutting your PC or Browser down for weeks. It that causes issues I think Mozilla should have that on low priority.
I use Brave on Linux mainly because I cant justify testing my webdev stuff not con Chromium and I tend to use the same Browser for everything, its also faster.
Mozilla like so brag about speed but I think the lost objectively measured to Blink a looooong time ago. Servo was given to the Linux Foundation and is far from ready. When its ready it will probably be pretty fast.
Firefox has a sessionrestore.js and also a sessionrestore.bak. ( And also sesstionrestore.bak2 if I remember correctly )[1] It is the only browser that took session restore seriously because around ~16 years ago an idiot constantly went on Mozillazine and Bugzilla to file crash report of lost sessions that could have thousands of tabs.
If your sesstionrestore crashed or get wiped, i.e you restart your browser and those tabs were not there, you could also copy and past the .bak files and rename it as .js. It wont be everything you had since the bak file may have been a few hours old. But at least you got something back.
As to crashing. In the old days it was some tabs in the background doing JS with memory leakage. But if I remember correctly Firefox now pause Tabs that is unused for long period of time. If it isn't background Tabs that is causing problem. I would suggest similar to what I wrote to Animats, make a new Firefox profile and migrate all your History, Cookies etc to the new profile and see if it improve things. This used to be a manual process but I believe recent Firefox has made this easier with Firefox Retune or Refresh ( Sorry all of this are on top of my head you will have to do some Google search for the actual name)
If I were to rate Browser stability, it would be Firefox > Chrome > Safari. On both MacOS and Windows. The same ranking for session restore function where I have lost multiple sessions on Safari over the years. And in case anyone wondering why Safari is not stable and that may not be their experience, it is that something on MacOS ( the OS itself ) sometimes triggers Safari to reload all the Tabs even if they were originally sitting idle. This create huge I/O spike and generally leads to crashing or halt for a long period of time. Other than that it is pretty much on par with others.
[1] Those file and extensions names were something on top of my head so you have to google it to double check
[1] https://blog.mozilla.org/en/mozilla/introducing-firefox-quan...
> Firefox hangs after using it for a long time
> Firefox may hang if left open for long periods of time. To fix the issue, restart Firefox.
So I can choose between closing all of my open tabs at the end of each workday or randomly losing them during the workday. Since having my tabs open when I start work helps me jump back in, I've settled on randomly losing my tabs.
They also suggest using their session restore feature after a hang, but with this type of crash, Firefox is never able to restore your tabs. It also doesn't record the crash report in about:crashes. Overall, not great and it has me thinking of trying Brave.
1. https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-re...