Bug 499776

Summary: Screen sharing a fullscreen game window with chromium or discord grinds the game to halt
Product: [Plasma] kwin Reporter: Dick Tracey <traceydick>
Component: xwaylandAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: xaver.hugl
Priority: NOR    
Version: 6.2.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dick Tracey 2025-02-10 19:38:33 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Start a game (so far tried various native and proton/wine titles on Steam) in fullscreen
2. Go to meet.google.com on Chromium (or discord) and share the window of that game
3. Go back to the game

OBSERVED RESULT

The game rendering essentially halts when using a single screen.
With dual screens, the game renders at a stuttering, very low FPS

EXPECTED RESULT

Game should run smoothly


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.12.12
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION

Using nvidia-open drivers.
Not a VRAM issue, nvtop reports only half of my VRAM being used.
Same configuration on X11 (with kwin_x11) works without any issues.
I don't see xwaylandvideobridge being used in the list of processes.
Comment 1 Dick Tracey 2025-02-10 19:40:20 UTC
Another data point: when sharing screen with Don't Starve Together in windowed mode, everything works fine.
When I toggle fullscreen from the game's graphics settings, the rendering halts.
Comment 2 Zamundaaa 2025-02-10 20:43:21 UTC

*** This bug has been marked as a duplicate of bug 495287 ***