Why is Firefox not re-writing recovery.jsonlz4 file?
I am running Firefox 65.0.2 in Windows 7 Professional 32-bit. It is 8:16PM on 03/18/2019. The recovery files have timestamps:
03/05/2019 03:09 PM 2,049,220 previous.jsonlz4 03/14/2019 09:36 AM 2,124,762 recovery.baklz4 03/14/2019 09:37 AM 2,124,716 recovery.jsonlz4
Why is Firefox not writing a new file when I open or close a tab? Is there anything I can do right now do get diagnostics on this problem? I believe that tomorrow I may be installing Windows patches and have to reboot, and restarting Firefox will lose all diagnostic data. Thanks.
Επιπρόσθετες λεπτομέρειες συστήματος
I ALWAYS run FF in safe-mode.
- Πλατφόρμα χρήστη: Mozilla/5.0 (Windows NT 6.1; rv:65.0) Gecko/20100101 Firefox/65.0
JScher2000 wrote, in a reply above. "You could check Firefox's Browser Console for any error messages related to the session store saving function. ..."
I use cntl-shift-k to open a console, but I have no idea what do do after the console pop-up windows appears.
Sorry, that's the "Web Console, which is tab-specific. The Browser Console is opened using Ctrl+Shift+j.
I have no idea what you're looking for, either, because I've never seen anyone else report this problem.
By the way, cor-el posted a method to capture a session history snapshot using the Browser Console, so it may be handy to become familiar with it in case you need to save your own recovery.json file:
Are you sure you look in the correct Firefox profile folder?
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder
jscher2000, I will use cntl-shift-j the next time the problem occurs. When the problem occurs, FF is running slowly and has other problems. And I will post info here after the next occurrence.
cor-el, I am looking in the correct folder. I have written a script "sd" to do a "dir /od" in the correct sessionstore-backups directory. And I have a similar script "sdr" to look for sessionstore.jsonlz4 in the parent directory. And I have a "cdsess" script to do a "cd" into the sessionstore-backups directory, where I frequently make copies of the current restore files, in case one gets corrupted. I got tired of entering manually the directory name and its path.