[KDE] Addons UI can freeze Firefox [wl_buffer exhaustion]
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: qsjt0nvb05it, Unassigned)
References
(Blocks 2 open bugs)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
Open some addon like uBlock Origin or Simple Tab Group, and play with the UI for seconds to minutes, then Firefox will freeze
Actual results:
Firefox will freeze
Expected results:
Firefox should not freeze
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Hello,
I could not reproduce the issue on my end on the latest Nightly (108.0a1/20221102174350) and Release (106.0.3/20221030091646) under Windows 10 x64 and Ubuntu 16.04 LTS.
I’ve installed both uBlock Origin and Simple Tab Groups and navigated through the extensions’ UI, using the extension functions and navigated through Firefox’s UI for about 15 minutes. Neither edition of Firefox froze.
Could you attach a video of what exactly you are doing when the issue occurs? Thank you !
Reporter | ||
Comment 4•2 years ago
|
||
Open ublock origin and hover the cursor on the icons, until the text pops up, and repeat for several times. Then my Firefox freezes.
Comment 5•2 years ago
•
|
||
Thank you for the additional info !
I installed a Simplified Chinese language pack as that seems you have on your end and then uBlock Origin. Then I kept hovering over the pop-up buttons so the label was displayed, for a good 8-10 minutes. Still Firefox did not freeze on my end.
Tested this on Release (106.0.3/20221030091646) under Windows 10 x64 and Ubuntu 16.04 LTS.
Reporter | ||
Comment 6•2 years ago
|
||
I'm using KDE + Wayland and Firefox with Wayland enabled (MOZ_ENABLE_WAYLAND=1), and I can reproduce this bug on this platform. I can't reproduce it on KDE Wayland + Firefox X11 (XWayland), KDE X11 + Firefox X11, or GNOME Wayland + Firefox Wayland. Looks like it only affects KDE Wayland + Firefox Wayland. I also noticed that the popup label will flicker on KDE Wayland + Firefox Wayland, but not on other platforms. I'm using the latest Flatpak version of Firefox. I'm using Fedora 36 and KDE 5.25.5 + Wayland.
Comment 7•2 years ago
|
||
Hi Emilio,
this bug seems to only happen with wayland, do you know who we could ask help to investigate what Firefox may be doing differently that could trigger this issue? (or if you have seen any other bugzilla issue similar to this one that may be triggered from Firefox UI that doesn't belong to addons)
Comment 8•2 years ago
|
||
Does this reproduce on Nightly? Looks a lot like bug 1717451
Comment 9•1 year ago
|
||
Please attach crash ID when Firefox is frozen:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Getting_Mozilla_crash_report_from_running_or_frozen_Firefox
Thanks.
Updated•1 year ago
|
Reporter | ||
Comment 10•1 year ago
|
||
(In reply to Martin Stránský [:stransky] (ni? me) from comment #9)
Please attach crash ID when Firefox is frozen:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Getting_Mozilla_crash_report_from_running_or_frozen_Firefox
Thanks.
I run the command "kill -s 11 $(pidof firefox)" when Fierfox is frozen, and Firefox closes, and the window says
Firefox had a problem and crashed. We'll try to restore your tabs
and windows when it restarts.
Unfortunately the crash reporter is unable to submit a crash report.
Details: The application did not leave a crash dump file.
And I didn't get a new crash report in about:crashes. I tried to run this command when Firefox is running normally, and I didn't get a crash report either.
Reporter | ||
Comment 11•1 year ago
|
||
I created a new profile in about:profiles and download uBlock in the new profile, and I can reproduce the bug.
Reporter | ||
Comment 12•1 year ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #8)
Does this reproduce on Nightly? Looks a lot like bug 1717451
I downloaded nightly and I can reproduce this bug. And I can get and upload the crash report. Report ID is bp-7441f81c-1431-45d2-b62a-61f120221127
However I cannot get a crash report in Flatpak version.
Comment 13•1 year ago
|
||
Clearing the needinfo assigned to me, the reported took care of attaching a crash report in comment 12.
Comment 14•1 year ago
|
||
Yes, this deadlock is caused by wl_subsurface exhaustion - we're waiting for free wl_buffer but we're not getting one from compositor.
Updated•1 year ago
|
Description
•