upgrading firefox loses all windows and tabs
Categories
(Firefox :: Session Restore, defect)
Tracking
()
People
(Reporter: mozilla-sp, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0
Steps to reproduce:
Download Firefox 127. Quit Firefox 115. Open Firefox 127 on same profile.
Actual results:
All my tabs and windows were forgotten. There was no "restore previous session" option on the menu, it was unavailable. I closed 127 and reopened 115 hoping to make a list of my open tabs and windows, and it told me I was not allowed to open an older version anymore unless I created a brand new profile. All my tabs and windows are permanently lost and unrecoverable.
Expected results:
It should have not wiped out all my open tabs and windows, or, it should have allowed me the option of reopening 115 to the same profile so I could find a way to record what they are. It shouldn't have completely and irrecoverably destroyed the record of what I had open and intentionally stood in my way to ensure I couldn't ever retrieve them in any way.
|
||
Comment 1•8 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Session Restore' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•8 months ago
|
||
Hello.
This may be because of a bug that we have recently fixed in 127.0.2.
Are you still able to reproduce this issue while using 127.0.2 FF?
I have just resolved the same issue.
Updating from 126 to any later version caused several malfunctions including blank pages and being unable to properly load the profile.
Speculation:
The reason was probably inconsistent data in the keystore.
It was probably caused (speculation) by:
- not having a primary password set and
- being logged into FireFox Sync
I was able to fix it by: deleting the key4.db in my profile folder.
This logged me out of the Sync account.
After that the update to 128 was smooth sailing.
|
||
Comment 4•7 months ago
|
||
This is tracked in bug 1901899.
Description
•