Bug 442433 - Chromium-based (electron) web browsers hang when rendering fullscreen
Summary: Chromium-based (electron) web browsers hang when rendering fullscreen
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.22.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-14 14:39 UTC by Ad
Modified: 2021-09-21 09:09 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ad 2021-09-14 14:39:37 UTC
SUMMARY
I am not quite sure it's a bug rather than a problem with my configuration, but for a couple of weeks (the problem didn't appear before) any chromium-based web browser run through Wayland with `--enable-features=UseOzonePlatform --ozone-platform=wayland` -- the usual way of forcing an electron application to render to the Wayland client -- completely freezes when setting a running video stream to fullscreen. The only escape hatch is Alt-F4 out of it.

STEPS TO REPRODUCE
1. From a tty, launch a Wayland session: `dbus-run-session startplasma-wayland`
2. Run microsoft-edge-beta (rpm source: 94.0.992.19-1) or brave-browser (rpm source: 1.29.80-1) with the flags `--enable-features=UseOzonePlatform --ozone-platform=wayland`
3. Point the browser to an embedded video, click the player widget to set it to fullscreen.

OBSERVED RESULT
The browser completely hangs. (Wasn't happening a couple of weeks ago)

EXPECTED RESULT
The browser runs the video fine.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210910
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15.5 Gio of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Comment 1 Sok Ann Yap 2021-09-20 21:08:24 UTC
This is a bug in kwin 5.22.5, and has already been fixed in kwin 5.22.90: https://bugs.chromium.org/p/chromium/issues/detail?id=1248049
Comment 2 Ad 2021-09-21 09:08:49 UTC
As I can see! Thanks for your quick reply, feel free to close (if the attempt I am about to make fails).