SUMMARY: kwin_wayland always takes a lot of % cpu (can be observed with "top" or "htop" commands) on Nvidia prime laptop, external monitor with DisplayPort. % decreses by a lot when deleting Klipper's history. STEPS TO REPRODUCE: right click the klipper's icon in the systray, delete the history OBSERVED RESULT: cpu usage of kwin_wayland goes from 70% to 5%-20%. Stays very high only when watching videos via web browsers. I don't know how this is related. Found somebody else who had the same situation: https://forum.manjaro.org/t/plasmashell-and-kwin-wayland-use-lots-of-cpu-if-no-window-is-open/162038 SOFTWARE/OS VERSIONS: Tumbleweed, latest available KDE 6.0.x.
Can you check again in Plasma 6.1 once it's released in about a week? Some "high CPU usage" bugs relating to the clipboard were fixed there. thanks!
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!
(In reply to Nate Graham from comment #1) > Can you check again in Plasma 6.1 once it's released in about a week? Some > "high CPU usage" bugs relating to the clipboard were fixed there. thanks! Hi Nate, sorry for being late, but the updated has been rolled out only now on my system. I still see high CPU usage, so I am not sure if it's actually working. This usage is shown via "top" in a terminal, unless I should use a different method.
Ok, thanks. What's in your history? How large is it?
(In reply to Nate Graham from comment #4) > Ok, thanks. What's in your history? How large is it? Right now only 25 copied entries. I can see kwin_wayland going from 25 to zero or max 12% while using "top" in a terminal emulator (konsole) once I erase history. However, the general performance have improved after updating to 6.1.1, only this Klipper parts remains (which might be acceptable maybe).
Just stumbled into the same bug with kwin version 6.1.3 on Fedora 40. CPU usage goes to almost 0 just after clearing Klipper history. I'm using NVidia too. System info: ========== Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.2 ГиБ of RAM Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2 Manufacturer: ASUS
Can you run plasmashell with WAYLAND_DEBUG=1 envvar set and attach the output to this bug report? After providing the output, please reset the bug report status to REPORTED
(In reply to Vlad Zahorodnii from comment #8) > Can you run plasmashell with WAYLAND_DEBUG=1 envvar set and attach the > output to this bug report? After providing the output, please reset the bug > report status to REPORTED I want to see if I can help too. Should I use startplasma-wayland WAYLAND_DEBUG=1? I might need more info on how to use this.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.