Bug 472407

Summary:	Walyand: Screencasting causes KWin to take up 100% of a single CPU core
Product:	[Plasma] kwin	Reporter:	Naxdy <xnaxdy>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ahiemstra, arttuc, nate, xaver.hugl
Priority:	NOR	Keywords:	regression, wayland-only
Version First Reported In:	5.27.6
Target Milestone:	---
Platform:	NixOS
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Naxdy 2023-07-19 19:31:24 UTC

SUMMARY
The commit https://invent.kde.org/plasma/kwin/-/commit/23806d31e23d2ef2bc8344114feb6d27364cdc01 has introduced a regression that can be observed on my system that manifests itself as KWin taking up 100% of a single CPU core (and dropping frames) when screencasting.

Reverting the mentioned commit has completely resolved the issue for me.

STEPS TO REPRODUCE
0. Log in to Plasma Wayland session
1. Begin screencasting (I used rectangular region which is scheduled for 6.0, but fullscreen produced the same issue for me - I used OBS to test this)

OBSERVED RESULT
KWin takes up 100% of a singe CPU core (thread), mouse movement is choppy, and journalctl --user shows KWin is struggling with frame drops.

EXPECTED RESULT
Screencasting is smooth, does not impact desktop usage, and does not take 100% of a single CPU core.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS
(available in About System)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
-

Comment 1 Naxdy 2023-07-19 19:32:05 UTC

Also, possibly related to: https://bugs.kde.org/show_bug.cgi?id=467574

Comment 2 Zamundaaa 2024-02-12 15:19:02 UTC


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