After updating Firefox 121=>122 extreme cpu load and crash on startup with many tabs
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
People
(Reporter: andre.saenger, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
Updated from Firefox 121 to 122 on Ubuntu 20.04 via regular system updates.
Restarted Firefox with the previously opened profile were many tabs and windows were active.
Actual results:
Firefox shows extreme high cpu usage and behaves unresponsive, until it crashes after a couple of minutes.
Starting this profile in safe mode works.
New Profile works
Disabling extensions makes no difference.
Reverting back to firefox_121.0.1+build1-0ubuntu0.20.04.1_amd64.deb and starting with firefox --allow-downgrade allows to load the old state as expected.
Expected results:
Expected to be able to continue where I left off before the update.
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
Just to be sure, do I understand correctly that Firefox 122 with new profile works correctly and problem is with old profile only?
Thanks.
|
|
||
Updated•2 years ago
|
|
Reporter | |
Comment 3•2 years ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #2)
Just to be sure, do I understand correctly that Firefox 122 with new profile works correctly and problem is with old profile only?
Thanks.
Yes, only happened with the old profile with many open tabs and windows I was working in before the update. With a new profile or another old profile where no big session was stored it didn't show this problem.
|
||
Comment 4•2 years ago
|
||
Hello, my Firefox also became very unstable since 122 update. I am using Windows 11 however, but a couple of times a day my window fades and the only way to make it working again is to kill the process by any of the methods available. I haven't tried any of the precautions mentioned by OP, but I am happy to assist with finding the cause of my instability. I will probably just try to downgrade to 121 for a while and see if it helps… Oh, another common thing is I have many tabs open (694 right now, 9 of them pinned), but my Firefox doesn't crash right at the start, but after a couple of hours.
|
|
||
Comment 5•2 years ago
|
||
Please try to use mozregression tool to find broken commit:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
You may even pass your profile to use for testing.
Thanks.
|
|
||
Comment 6•2 years ago
|
||
(In reply to Martin Stružský from comment #4)
Hello, my Firefox also became very unstable since 122 update. I am using Windows 11 however, but a couple of times a day my window fades and the only way to make it working again is to kill the process by any of the methods available. I haven't tried any of the precautions mentioned by OP, but I am happy to assist with finding the cause of my instability. I will probably just try to downgrade to 121 for a while and see if it helps… Oh, another common thing is I have many tabs open (694 right now, 9 of them pinned), but my Firefox doesn't crash right at the start, but after a couple of hours.
Please file a new bug for Windows, this is for Linux only.
Thanks.
Description
•