Open
Bug 1489567
Opened 6 years ago
Updated 2 years ago
Lost session (may be related to clicking an IRC link while Firefox was restarting)
Categories
(Firefox :: Session Restore, defect, P2)
Firefox
Session Restore
Tracking
()
NEW
People
(Reporter: botond, Unassigned)
References
(Blocks 1 open bug)
Details
Earlier today I lost my Firefox session (all my tabs), without being able to restore them via Session Restore, Recently Closed Tabs/Windows, or anything similar. I was eventually able to restore my session manually from sessionstore-backups (using the instructions here [1]). Here's what I did: 1. Clicked Hamburger menu -> Restart to update Nightly. 2. The small "Firefox is installing updates" dialog appeared as usual. 3. _While_ that dialog was open, I clicked on a link in my IRC client (which is Konversation). 4. The end result was two Firefox windows, one with the link I opened, the second empty. I verified that both belong to the same profile. My original session was gone. I assume that when I clicked on the IRC link, the Firefox executable was invoked while the update was happening, and that messed things up? My Firefox version is a recent Nightly (more specifically, an ASAN Nightly, though I assume that's not material) running on Debian stable. [1] https://support.mozilla.org/en-US/questions/1189759
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(mdeboer)
Comment 1•6 years ago
|
||
Could this have been bug 1489471? The second window might have been your restored session and you might have been able to drag invisible tabs out of it.
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #1) > Could this have been bug 1489471? The second window might have been your > restored session and you might have been able to drag invisible tabs out of > it. I wasn't using WebRender (it makes nouveau sad).
Comment 3•6 years ago
|
||
Hmm, I think that launching the second Firefox instance during upgrade reveals a race condition that should be reproducible on Windows too... but not easily (which is why I'm marking this as a P2 for now).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•