firefox91 hangs after a while
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: udovdh, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
40.88 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
While browsing the web using Firefox91, after a while the browser tends to become very sluggish to unresponsive.
Actual results:
Firefox was beyond usable, had to quit (alt-f4) and restart
Expected results:
No such hang.
Comment 2•3 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 revert this change in case you think the bot is wrong.
Comment 3•3 years ago
|
||
Please see https://support.mozilla.org/en-US/products/firefox/fix-problems/slowness-or-hanging and https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down , plus https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding , and report back.
Do you imply this is not a bug?
This worked well until a FF upgrade.
The box has plenty of RAM and CPU so 'resources' of that kind are not the culprit.
Comment 5•3 years ago
|
||
Please open about:support, click on "Copy text to clipboard" and paste it here. Thanks!
Yes, I did a downgrade to test if there is indeed a version issue hidden as well.
Please try Firefox 91 and try Firefox with new profile:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Test_Firefox_with_a_new_profile
Thanks.
Yes we run Wayland as Xorg does not support 4K very well.
We will first run this FF to see if the problem persists.
Then upgrade again to 91.
Then it is still a bug.
When an application cannot keep the settings proper so that the application starts to malfunction after a while...
That is a bug.
I.e.: FF itself should be able to sanitize the configuration/settings/etc.
The addons should have a similar function.
Comment 10•3 years ago
|
||
It happens something very similar to me that started on FF 91 with Wayland. @udo do you have webrender enabled?. I think the issue I'm hitting is with webrender on. I've already opened an issue about this here https://bugzilla.mozilla.org/show_bug.cgi?id=1726357
Reporter | ||
Comment 11•3 years ago
|
||
When I look over about:config I see some (!) webrender items enabled.
Only the failureid's are modified, the rest looks stock.
Comment 12•3 years ago
|
||
Can this be fixed by disabling widget.wayland.vsync.enabled on about:config and restarting Firefox?
Reporter | ||
Comment 13•3 years ago
|
||
Will need some testing...
Reporter | ||
Comment 14•3 years ago
|
||
(In reply to Darkspirit from comment #12)
Can this be fixed by disabling widget.wayland.vsync.enabled on about:config and restarting Firefox?
Does not fix the hangs.
Comment 15•3 years ago
|
||
(In reply to udo from comment #14)
Does not fix the hangs.
Thanks, that's a very valuable infomation. If you are willing to test two more things (one at a time), that would be really great:
- Using software rendering (setting
gfx.webrender.software
totrue
), so we know if it has something to do with hardware acceleration (widget.wayland.vsync.enabled
can be enabled again / set to default). - Using the X11/Xwayland backend by not setting
MOZ_ENABLE_WAYLAND
- so we know if it's something Wayland related.
Reporter | ||
Comment 16•3 years ago
|
||
Thanks Robert.
I mad the change for gfx.webrender.software.
For MOZ_ENABLE_WAYLAND I need more info on how/where to change.
Please check the performance troubleshooting steps from:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Firefox_performance_issues
Thanks.
Reporter | ||
Comment 18•3 years ago
|
||
(In reply to udo from comment #16)
Thanks Robert.
I mad the change for gfx.webrender.software.
For MOZ_ENABLE_WAYLAND I need more info on how/where to change.
gfx.webrender.software does not make the issue go away.
Comment 19•3 years ago
|
||
bug-1690367-rollout-moving-webrtc-networking-functionality-into-i-release-87-100: active
bug-1725376-rollout-https-rr-rollout-release-91-91: active
pref-rollout-geolocation-os-api-61-64-linux-1527748: active
rollout-increasing-normandy-skew-out-changes-from-15-m-release-73-75-bug-1616898: active
rollout-monitor-v2-1505837: active
Can this be fixed by disabling network.dns.force_waiting_https_rr, network.dns.use_https_rr_as_altsvc, network.dns.upgrade_with_https_rr and restarting Firefox?
Comment 20•3 years ago
|
||
Could this be the same bug as this one: https://bugzilla.redhat.com/show_bug.cgi?id=1996542
Reporter | ||
Comment 21•3 years ago
|
||
Also happens when I am not at the keyboard, when FF is active.
Reporter | ||
Comment 22•3 years ago
|
||
Simply play a video stream from e.g. youtube for a while and the issue should appear.
Updated•2 years ago
|
Description
•