Closed Bug 1740223 Opened 2 years ago Closed 3 months ago

When leaving Firefox on overnight, it sometimes is frozen the next morning

Categories

(Firefox :: Session Restore, defect)

Firefox 94
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: oukourj, Unassigned)

Details

(Whiteboard: [QA-not-reproducible])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

On Windows 10 21H1, leave Firefox 94 open overnight on a turned on computer, with a few open tabs and 4 pinned tabs.
Nothing playing.

Actual results:

Firefox is Frozen when logging back into the computer.
Other applications are unaffected.
Firefox still shows the full interface but nothing responds.
After minimizing and maximizing it again it shows a blank screen. It is totally frozen and has to be killed.
When opening it again, it has forgoten the pinned tabs, and didn't save the last session (can't re-open tabs using history).

Expected results:

Shouldn't have froze.

Hey Alexandre,
I tried reproducing this issue on the latest versions of Firefox Nightly 96.0a1 (2021-11-09), beta 95.0b5 and release 94.0.1 by leaving it on for 7-8 hours with pinned tabs as well but I do not encounter the freeze.

Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .
Also a fresh new profile could help. You can find more about creating a new profile here : https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile .
If possible, you can test this issue on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .

Flags: needinfo?(oukourj)
Whiteboard: [QA-not-reproducible]

Hi, I admit it's a very tricky case, because it happens maybe 5% of the nights I leave it on. I will try to give more info the next time (most probably all I can give is the open tabs list, because as far as I can see, Firefox crashes in a way that makes it log nothing).
If there are logs or any info I can extract for next time let me know.

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.

Component: Untriaged → Session Restore

[Original Poster here with a github account because BugZilla password requirements are CIA-level so I forget them everytime, and I discovered I can log in with github.]

So, the case just happened again, for the first time when I'm (kindof) using the computer.
It happened while I was afk for less than 10 minutes.
The computer wasn't locked when I came back, and Firefox had frozen.

I have more details on the symptoms :
actually, Firefox is not totally frozen, it will just refuse ANY input (mouse, including 'hover', and keyboard), and it will refuse it only for the Window that was open.
It means that I can open another Window by right-clicking the Firefox icon in the taskbar, and this new Window works normally.
I can also open a new tab to the "frozen" windows using the same trick, the tab opens, and if the tab requested was a website, it loads the website. But it doesn't unlock the situation, no input will be taken.
Another detail that points to a bug was mentionned in my OP : closing Firefox (again, by right-clicking the icon in the taskbar) will immediately close it, and reopening it will have forgotten all the pinned tabs and history (at least, the "Restore previous session" history, didn't check the rest).

I triple-checked that no physical input was locked (nothing physically pressing on the mouse or keyboard).
All the other apps, Windows, everything works perfectly.

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.

For more information, please visit BugBot documentation.

Status: UNCONFIRMED → RESOLVED
Closed: 3 months ago
Flags: needinfo?(oukourj)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.