[134.0a1] Intermittent session loss after non-rendering "ghost" session
Categories
(Firefox :: Session Restore, defect)
Tracking
()
People
(Reporter: hikaph+mozilla, Unassigned)
Details
Attachments
(3 files)
Steps to reproduce:
This issue is unfortunately not always reproducible nor is it obvious to me how to send any diagnostic information in the bugged state. I wish I had kept notes, but basically it happens less than a few times a month, but has now happened maybe twice in two weeks.
User agent:
Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Build ID: 20241122092800
-
Configure Firefox to always restore your previous session on startup.
-
Quit the browser.
-
Start the browser and wait for the window to spawn.
Actual results:
-
The window presented but the contents were not rendered.
-
This is visually clear to me in my desktop environment (swaywm with a violently monochrome pink background, so an all-pink window means that the surface isn't rendering properly).
-
Browsing appears to work — blindly typing the sequence to open a new tab (with the URL bar focused), entering some random search term, and pressing "enter" changes the window title to reflect that the relevant query was passed to my search engine of choice. The window remains uniformly pink, though.
-
Quitting the browser at this point and restarting it causes a brand-new session to open (i.e. Nightly appears to lose all my tabs).
Expected results:
The browser should have opened and worked as normal. Session should not be lost.
|
||
Comment 1•14 days 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•10 days ago
|
||
(In reply to Kalvin Lee from comment #0)
- The window presented but the contents were not rendered.
Thanks for the report. I wonder if there are any exceptions being logged in this state. This MDN article has instructions on enabling and using the Browser Toolbox which is one way to get to the browser console? (distinct from the devtools console).
The other place it might be useful to look is in your profile directory (the location is linked in the about:support page) where you should have a sessionstore-logs directory with error log files. If you have those with timestamps that match the times you ran into this issue, can you attach them here?
|
Reporter | |
Comment 3•8 days ago
|
||
|
|
Reporter | |
Comment 4•8 days ago
|
||
|
|
Reporter | |
Comment 5•8 days ago
|
||
|
|
Reporter | |
Comment 6•8 days ago
|
||
As luck would have it I hit this just now.
I'm sorry to say that I couldn't activate a browser console in the bugged state. I did test it out when Nightly was working yesterday and Ctrl + Alt + Shift + I did spawn the window. It simply didn't acknowledge the keypresses in the bugged state, I'm afraid. (It's working again now that I've brought it out of the bugged state.)
I've attached the sessionstore-logs/ from
- when it entered the bugged state (
its-gone-pink-just-now.txt) - the first of two files after a restart into working, session-dropped state (
is-this-on-quit.txt) - the second of the two (
is-this-on-start.txt)
Description
•