History being wiped whenever Firefox updates
So, whenever my Firefox updates, it seems that it completely wipes my history, and deletes all my tabs, despite it being set to "re-open previous tabs on launch".
This has happened multiple times now and is really not fun. Do I just need to make bookmark folders for everything I do? Because having everything randomly delete itself, without even a session restore in the backups folder of my firefox profile, isn't ideal.
I do have a sessionstore error for this, where I presume the problem is laid out.
1784409622095 SessionStore WARN SessionWriter.write, Caught exception:: NotFoundError: Could not move `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore.jsonlz4' to `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore-backups\previous.jsonlz4': source file does not exist (NS_ERROR_FILE_NOT_FOUND) No traceback available 1784409622095 SessionStore ERROR Could not write session state file : NotFoundError: Could not move `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore.jsonlz4' to `C:\Users\SUCKS TO SUCK\AppData\Roaming\Mozilla\Firefox\Profiles\sphzxgst.dev-edition-default\sessionstore-backups\previous.jsonlz4': source file does not exist (NS_ERROR_FILE_NOT_FOUND) No traceback available
All Replies (3)
How do the other timestamps look like in your profile folder? No other issues with the roaming profile, or the system in general? Was the error captured above really meant to happen on the timestamp logged, which presumably is mid–July?
Notably the sessionstore files and folders do not contain history, that's in places database — so if you're losing both, there's wider profile directory corruption going on than a single feature–specific issue:(
Could you open a bug to make sure engineers can get in touch with you in case they'd want to inspect the profile data or logs more closely, so this is tracked?
If you're having repeated problems with the updater writing the roaming location, consider using the Microsoft Store–provided Firefox installation, which, while having also the same opaque profile folder handling as the roaming profiles, manages the updates on its own, so these should be completely invisible to the actual browser.
No other issues with the system at all, and I'm not too sure what other logs are useful to provide for the bug report. Is there anywhere in specific I should make it, since I'm using the Dev edition of Firefox and not the default version, which is listed on Github? It happened once on the date I made this thread, and once about 2 weeks prior. It also just happened to me again, but that was preceeded by firefox using 14 gigs of ram momentarily before it, which does not usually happen.
It might be notable that every time its happened to me, I've exited firefox manually through the triple dot icon in the top right, whether through the exit icon or by update.
(Do you have any site data clearing enabled on shutdown? If so, would you be willing to download a separate Nightly, and use that for a test — that will serve you updates every day, so you can follow it more closely and in a rapid sequence as it will be restarting more frequently…)
This is the component to file a bug: bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Session%20Restore
Probably timestamps and sizes of any of those previous sessions, and anything interesting in the logs folder:
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.