Bug 446115 - kwin_wayland uses 10% of CPU all the time while OBS Studio is running but not recording my screen
Summary: kwin_wayland uses 10% of CPU all the time while OBS Studio is running but not...
Status: RESOLVED DUPLICATE of bug 469777
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: master
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-26 11:44 UTC by Patrick Silva
Modified: 2023-12-20 19:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2021-11-26 11:44:54 UTC 
STEPS TO REPRODUCE
1. use Wayland session
2. open OBS Studio
3. add 'Screen capture (Pipewire)' source to OBS Studio
3. open System Activity by pressing ctrl+esc and observe cpu usage of kwn_wayland

OBSERVED RESULT
cpu usage of kwin_wayland is 10% while OBS Studio is running. After closing OBS Studio, cpu usage immediately decreases to 1% or 2%.

EXPECTED RESULT
normal cpu usage while OBS Studio is running

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-40-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-3110M CPU @ 2.40GHz
Memory: 7,7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Comment 1 Zamundaaa 2023-06-12 11:13:08 UTC 
For KWin there's no difference between OBS running and getting the output stream, and OBS actually doing something with that output stream. In both cases it does exactly the same amount of work.

10% CPU usage for a video stream sounds like too much though
Comment 2 David Edmundson 2023-06-23 08:25:48 UTC 

*** This bug has been marked as a duplicate of bug 471364 ***
Comment 3 Nate Graham 2023-12-20 19:34:50 UTC 

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