Summary: | High CPU usage after starting Plasma | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Tareque Md Hanif <tarequemd.hanif> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | nate, tarequemd.hanif |
Priority: | NOR | ||
Version: | 5.27.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=452119 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tareque Md Hanif
2023-02-12 20:39:19 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. (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 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? > 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 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! 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! Fixed by removing picom. What is picom? This thing? https://github.com/yshui/picom |