Closed Bug 1106202 Opened 7 years ago Closed 7 years ago
Firefox hangs when windows resumes from hibernation
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20141127004008 Steps to reproduce: Open lid of laptop to resume from hibernate mode. FF Setting: - HWA off - Add-Ons off System: - Win7 SP1 (64) - Intel HD graphics 400 Actual results: After 3-4 times of resuming from hibernation Firefox hangs for 1 - 10(!) minutes. The Windows 7 loading ring appears and the tap bar gets overlayed by the title bar with the (Not Responding) message. After a couple of minutes most of the time a script error comes up - e.g. chrome://browser/content/browser.js:17027 sometimes a plugin container error. Expected results: Firefox resumes normally
OS: Mac OS X → Windows 7
Hardware: x86 → x86_64
It might be connected to bug 971345, but as Eldergias says that his issues start with FF 27, this computer was bought around the time FF 19 - 21 came out and had the described behaviour ever since.
I just saw in task manager, that when it hangs, it is very slow in getting back up to the memory required for the open tabs, etc.
Component: Untriaged → Session Restore
I also had this problem, and found this relevant blog post: http://asqueella.blogspot.be/2012/07/windows-7-resuming-from-hibernation-is.html. It describes exactly this problem, and correlates it to the "ThinkVantage Technologies Power Manager 6" software typically installed on Lenovo laptops. Short of uninstalling this software, this comment also describes a fix without uninstalling it, by setting a specific registry key: http://asqueella.blogspot.be/2012/07/windows-7-resuming-from-hibernation-is.html?showComment=1393430510370#c6260633152625448121 It also refers to this thread on Lenovo forums for more information: http://forums.lenovo.com/t5/ThinkVantage-Technologies/Bug-report-Power-Manager-causes-slow-performance-after-resuming/m-p/1349923/highlight/false#M24262 The registry fix (followed by a reboot) perfectly solved the issue for me. Resume from hibernation is now again as fast as it should be, and FF is immediately responsive.
Ah, you are a lifesaver Johan! Removed it and the machine finally works :) Marking this as invalid. Do you reckon it might be worth adding somehow to SUMO?
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You're welcome, I just ran into the same problem you did, and was lucky enough to find the relevant blog post :-). So mostly thanks to Nickolay Ponomarev for documenting this on his blog. Feel free to further spread documentation about this. An entry on SUMO might be very useful, to increase its discoverability. Also: maybe someone can contact Lenovo and / or ThinkVantage Technologies to get the bug fixed on their end? Alternatively: maybe something can be done in the FireFox codebase to prevent "Power Manager" from swapping out Firefox' memory when it does its "Fast Hibernation" trick (no idea what ... just pointing out the option for completeness).
(In reply to Johan Corveleyn from comment #5) > You're welcome, I just ran into the same problem you did, and was lucky > enough to find the relevant blog post :-). So mostly thanks to Nickolay > Ponomarev for documenting this on his blog. Yey Nickolay :) > > Feel free to further spread documentation about this. An entry on SUMO might > be very useful, to increase its discoverability. Done with some help from Noah :) https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding#w_firefox-hangs-when-windows-resumes-from-hibernation-on-thinkpad > > Also: maybe someone can contact Lenovo and / or ThinkVantage Technologies to > get the bug fixed on their end? I didn't find any useful link on this site as it was presented to me to submit it :( http://support.lenovo.com/au/en/contactus Even though a fix might already be in the latest version, just saw that it's from Feb. 2015 http://support.lenovo.com/au/en/products/laptops-and-netbooks/thinkpad-edge-laptops/thinkpad-edge-e430/downloads/DS014924
You need to log in before you can comment on or make changes to this bug.