Session Restore does not restore previously opened tabs when deleting history twice in a row
Categories
(Firefox :: Session Restore, defect)
Tracking
()
People
(Reporter: glsis-web, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
- Open a few tabs and load some sites.
- Close FF then open it again so that the previously opened tabs/sites are restored automatically.
- Delete history manually using the "Delete recent history..." function.
- Perform history deletion a second time as mentioned in step 3.
- Close then reopen Firefox.
Actual results:
All the tabs opened in the previous session are lost and FF opens with a blank page.
DETAILS: The first time you delete the history, the only session file that remains is recovery.jsonlz4, all other files, sessionstore.jsonlz4 , recovery.baklz4, previous.jsonlz4, are deleted.
Deleting the history the second time also deletes the recovery.jsonlz4 file, along with the sessionstore-backups directory, which then causes all open tabs to be lost, and the next time FF is restarted it opens a blank page.
PS: It's a problem that has been happening for years, so it's not limited to the latest version of FF.
Expected results:
Firefox should have saved the sessionstore.jsonlz4 file on closure and restored the previously opened tabs on the next restart.
It is also requested that in future versions of FF all session files (sessionstore.jsonlz4 , previous.jsonlz4, recovery.jsonlz4, recovery.baklz4) should never be removed by history deletion when there are opened tabs that are not just an empty tab or a tab with the domain set as the home page in FF preferences.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Session Restore' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•4 years ago
|
||
I was able to reproduce this issue using Firefox 96.0.3 on Windows 10 and MacOS 11.6
I'll set the flags and set it as NEW in order to get the development team involved in reviewing it.
Thank you for reporting!
|
|
||
Comment 3•3 years ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit auto_nag documentation.
If possible, could someone enable me, as the author of the initial message, the editing rights of Comment 0 and my additional comments ?
To edit the initial message I had to ask the user Dkl.
Considering that the Bugzilla platform keeps track of all the changes made to the text, it makes little sense not to enable the author of the bug report to make changes to his own message.
I did a check just now and it seems that the described problem no longer occurs and has been fixed, although I don't know from which version.
Can anyone confirm this bug is was solved ?
Description
•