Firefox causing Win 11 to restart following sleep
Categories
(Firefox :: Session Restore, defect)
Tracking
()
People
(Reporter: lim.leong, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
- Boot into Win11 Pro.
- Start Firefox 121.0.1
- Restore all previous open tabs in Firefox
- Start Visual Studio which then start WSL (Windows Sub System for Linux)
- Put computer to Sleep
Actual results:
Instead of waking up normally, Win11 did a complete re-start which resulted in critical errors in Event Viewer. Downgrading Firefox to Version 120.0.1 fixes the sleep reboot problem with all other things unchanged.
Attached are SysInfo and Events logs information
Expected results:
Windows should wake up normal instead of a complete reboot
Further Info: PC has an RTX2060 Super Graphics Card running the latest stable version of NVIDIA driver 546.65
Comment 2•1 year ago
|
||
Hi, please attach the content in that docx file as text or images that can be opened in the web browser without having to install an application that can open docx files - thanks.
Comment 4•1 year ago
|
||
I have attempted to reproduce this issue on a Windows 11 machine with Firefox Release v121.0.1 by restoring a random previous session, installing Windows Visual Studio, running the "wsl --install" command to install wsl, then going into sleep and restart. The system did not seem as it would start from scratch, but continued the previous session without issues.
I may be performing the steps in comment 0 incorrectly. Could you please help me reproduce it in order to confirm it?
- Do you think there could be specific web pages reloaded that might influence this behavior?
- How exactly should I start the WSL? What's the minimum necessary set-up?
- What do you mean by "complete restart"? Did your windows start-up and reopen all the applications you had open before?
- Where exactly did the critical errors appear inside Event Viewer?
- Is there anything else that might help us reproduce it?
Thank you for your contribution!
HI Daniel. Thanks for your time in investigating. I am also looking at the angle of a subtle power supply issue. I am thinking Firefox may be a contributing factor but may not the main causal factor. It could be that adding Firefox to the mix just tip things over the threshold of power supply can cause the problem of the PC doing a window re-start rather than a wake up from sleep.
To answer your questions:
- I have about between 20 - 30 tabs opened and I don't know if any of the tabs may be causing the issue.
- WSL (Windows subsystem for Linux) would need to be installed via wsl --install and then you will need to download a Linux distribution to use it. On my machine, I have used Ubuntu from Microsoft Store (https://apps.microsoft.com/detail/9PDXGNCFSCZV?hl=en-us&gl=US). To start WSL with Visual Studio Code, I start VSCode and connect to WSL by clicking the "WSL: Connect to WSL" button (following these steps https://code.visualstudio.com/docs/remote/wsl). Once VS Code is connected to WSL, it will automatically starts WSL as it is needed to run the code and then you can open any folder.
- "Complete restart". Instead of the PC waking up from sleep, the PC did a cold boot (as if the PC is turning on after a shutdown) resulting in error 41 Kernel Power in event viewer.
- The critical error 41 appeared in the "Critical Errors" section of Event Viewer.
- As I have said, I am going to try a new power supply as it could be a power supply problem and Firefox may not be the main contributing factor of the PC doing a cold reboot rather than waking up from sleep.
Hi There. I have now replaced the power supply in the PC and that seems to have fixed the "sleep/reboot" problem. I will continue to monitor this for a few more days. Perhaps this is a power supply issue rather than a Firefox issue, ie. Firefox simply adds a bit more load to the system causing the sleep/reboot rather than the root cause. Thanks.
Comment 7•1 year 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 8•1 year ago
|
||
Closing this report as WORKSFORME. If it reoccurs, please reopen this report. Thank you!
Description
•