Bug 457516 - Firefox locks up with kwin_wayland spiking in CPU when repeatedly right-clicking on extension popups
Summary: Firefox locks up with kwin_wayland spiking in CPU when repeatedly right-click...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.25.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL: https://bugzilla.mozilla.org/show_bug...
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-05 09:23 UTC by Schlaefer
Modified: 2024-04-24 12:55 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Example video: Firefox freezing with kwin_wayland cpu spike (381.57 KB, video/webm)
2022-08-05 09:23 UTC, Schlaefer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Schlaefer 2022-08-05 09:23:06 UTC
Created attachment 151128 [details]
Example video: Firefox freezing with kwin_wayland cpu spike

STEPS TO REPRODUCE
1. Open Firefox
2. Left click on an FF-extension icon that opens an extension-popup (for example the preinstalled Pocket extension)
3. Right click a few times on the open popup (activating and deactivating the context menu)

OBSERVED RESULT

After a few clicks Firefox stops responding and has to be force closed. Kwin_wayland starts to spike in CPU.

EXPECTED RESULT

Firefox stays responsible.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.18.16-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 5500 XT
Comment 1 Nate Graham 2022-08-05 18:25:43 UTC
Oh wow I can totally reproduce this.
Comment 2 Duncan 2022-08-07 00:22:58 UTC
I had seen this too (on gentoo, running all frameworks/plasma git-master using the gentoo/kde overlay live-git ebuilds, and also on wayland), but had chalked it up to forcing on some additional firefox gfx accel using about:config (running amdgpu driver with an old AMD Radeon Polaris-11 rx460 on an approximately decade old AMD fx6100  that has trouble with firefox/youtube 4k60 videos, 4k50's generally fine, so it needs all the accel help it can get).

Nate G: Per chance AMD gfx also (as me and original reporter), or Intel/nVidia thus confirming cross-gfx?  I know firefox at least was disabling certain gfx accel on kde/kwin_wayland on amdgpu, thus my trying to force it on, but am not sure what their current status is.  Anyway, could be related to that, if you're AMD gfx too.  If not it's gotta be unrelated to the previous firefox/amdgpu/kwin_wayland bugs.
Comment 3 Schlaefer 2022-08-07 11:31:28 UTC
I can also reproduce the issue on an Intel system:

Operating System: NixOS 22.11
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.15.59 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Comment 4 David Edmundson 2022-08-07 22:12:56 UTC
Can confirm.

hotspot shows kwin not doing anything special:
Handling a client event then doing nothing else.

WAYLAND_DEBUG=1 on ff shows an endless list of callback creation + done events

That all seems to be a sign of a firefox bug rather than a kwin one.
Comment 5 Schlaefer 2022-09-15 12:17:07 UTC
Since the indication it may be an FF issue I filed a bug there too: https://bugzilla.mozilla.org/show_bug.cgi?id=1790991
Comment 6 John Brooks 2022-12-13 23:09:33 UTC
I cannot reproduce this with kwin from git and Firefox 108.
Comment 7 Justin Zobel 2022-12-14 00:32:03 UTC
Can confirm with Fedora 37, kwin 5.26.4 and Firefox 107.0

Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.10-300.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Comment 8 Schlaefer 2024-04-24 12:55:54 UTC
Seems to work now, marked as dup and fixed by upstream. Closing.