Bug 465639 - High CPU usage after starting Plasma
Summary: High CPU usage after starting Plasma
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.27.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-12 20:39 UTC by Tareque Md Hanif
Modified: 2023-04-06 15:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tareque Md Hanif 2023-02-12 20:39:19 UTC
It's taking almost 60% CPU after starting Plasma from tty with startx.
There is a workaround, If I go to system settings, and set Vsync to anything else, the CPU spike stops.
The Vsync option was on "Automatic", so I change it to "Only when cheap", then it gets fixed.
If the Vsync option was on "Only when cheap", if I change it to "Automatic", it gets fixed.
I can see in htop that kwin_x11 is taking 50-60% CPU when the issue arises.

I can help by providing any profiling or other information.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kernel 6.1.11-arch1-1
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION:
GPU: Intel HD Graphics 620
Comment 1 Tareque Md Hanif 2023-02-17 10:42:11 UTC
I just updated Plasma to 5.27 on my laptop. And I see the same high CPU usage. But this time when I changed the "Latency" setting in the Compositor settings to "Balance of latency and smoothness". By default it was "Force smoothest animations". The VSync option is not there anymore.
As this commit (https://invent.kde.org)/plasma/kwin/-/commit/cf583aa3673cfca275b64d25c457d9e4a298c46c) suggests, I am guessing this will be fixed in Plasma 6.
Comment 2 Tareque Md Hanif 2023-02-17 10:43:39 UTC
(In reply to Tareque Md Hanif from comment #1)
> I just updated Plasma to 5.27 on my laptop. And I see the same high CPU
> usage. But this time when I changed the "Latency" setting in the Compositor
> settings to "Balance of latency and smoothness". By default it was "Force
> smoothest animations". The VSync option is not there anymore.
> As this commit
> (https://invent.kde.org)/plasma/kwin/-/commit/
> cf583aa3673cfca275b64d25c457d9e4a298c46c) suggests, I am guessing this will
> be fixed in Plasma 6.

Sorry, commit link corrected.
https://invent.kde.org/plasma/kwin/-/commit/cf583aa3673cfca275b64d25c457d9e4a298c46c
Comment 3 Nate Graham 2023-02-17 18:30:18 UTC
So when you change the latency setting to "Balance of Latency and Smoothness", the issue goes away?

FWIW I have the same GPU and can't reproduce the issue. Can you attach the contents of Info Center > Graphics > Window Manager?
Comment 4 Tareque Md Hanif 2023-02-26 09:07:39 UTC
> So when you change the latency setting to "Balance of Latency and Smoothness", the issue goes away?
Yes. Here is the output of "Window Manager" in Info Center.
https://invent.kde.org/-/snippets/2516
Comment 5 Bug Janitor Service 2023-03-13 03:45:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-03-28 03:45:43 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 7 Tareque Md Hanif 2023-04-05 21:54:59 UTC
Fixed by removing picom.
Comment 8 Nate Graham 2023-04-06 15:17:00 UTC
What is picom? This thing? https://github.com/yshui/picom