Open Bug 1464685 Opened Last year Updated 4 months ago
Firefox fails to load large session store
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180524181234 Steps to reproduce: 1. Firefox crashed (not what this report is about) 2. When starting up again, Firefox failed to properly load the session restore data in the about:sessionrestore tab, likely because that data was too large 3. I decompressed sessionstore.jsonlz4 and extracted the formData from the about:sessionrestore tab in it and saved that as sessionstore.js. 4. Tried to start Firefox using the resulting file, but it (silently) failed to load the session and just started an empty session (re-compressing as to jsonlz4 did not make difference). 5. Stripped some extension cache data stored by the Tree Style Tab extension, see issue filed against TST for details (https://github.com/piroor/treestyletab/issues/1907 "TST bloats Firefox session store file"). In short, this decreased the uncompressed size of sessionstore.js from 257MiB to 38MiB. 6. Tried to start Firefox using the resulting file, and it worked. In addition, the session restore data that actually was in the file was ~1.5 months old (despite being written recently), so while just a guess, it seems like Firefox might have issues writing session store files that are too large as well. Actual results: Firefox discarded my session. Expected results: Firefox should have loaded the session without issue. Note that while I filed an issue against the TST extension for bloating the file size of the session store, Firefox being unable to load it properly should still count as a bug.
Priority: -- → P4
Great to see this bug, had this issue a few weeks ago after a crash, but have not yet reproduced Firefox creating a file it couldn’t read as it stopped writing above the size it could read Bug 1472470. Maybe while it is in the state being unable to write because of too much data, and then the browser is closed and it writes a file too big that it otherwise would avoid?
You need to log in before you can comment on or make changes to this bug.