Created attachment 114997 [details] Xorg log (I tried to find already existing reports referring to the observed problem, but could not find any. I attached my Xorg.0.log for details. System is a, in comparison still not-that-slow, 3.0 GHz Intel Core i7 3540M. OpenGL and 3D effects are enabled and run smoothly.) As soon as plasmashell shows an indicator for an ongoing copy or even download operation, using the spinning circle, the CPU load goes up to nearly 100% on one core, split between the plasmashell and the Xorg processes. This seems to indicate an overly large and frequent amount of repaint requests being made, possibly for the spinning indicator. It's sufficient to download a larger file using Chrome via a slow internet connection (I'm currently on a slow mobile link during this weekend.) and the load will go to 100%, even though the download is just drippling / sometimes even stalled for several seconds. I'd assume updating the indicator 25 or 30 times a second would be more than enough for a smooth animation, so why the high load?
Supposedly fixed. See bug 356479
(In reply to Dr. Chapatin from comment #1) > Supposedly fixed. See bug 356479 This other bug was marked as "Fixed" in 2016 and a second time (after reopening) in 2017. I'm using Plasma 5.13.4, however, and the problem still persists. Bug 356479 comment 90 even requests to open a new bug if the symptoms still occur, as they will probably have a different cause in this case. I'm not sure how to provide any additional meaningful information to debug this issue, though...
>I'm not sure how to provide any additional meaningful information to debug this issue, though... Then we may as well close this. There are some other more specific bugs about CPU usage that we are working on.
(In reply to David Edmundson from comment #3) > > I'm not sure how to provide any additional meaningful information to debug > > this issue, though... > Then we may as well close this. There are some other more specific bugs > about CPU usage that we are working on. I'm willing to provide any additional information which you need, I just have no idea what this might be. To reproduce this issue, it's sufficient to download a file using Chromium and CPU-usage of Plasmashell will skyrocket.
Ok, can you provide a perf trace
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 set the bug status 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!
@David: Do you mean this by "perf": https://perf.wiki.kernel.org/index.php/Main_Page ? Never used it but will try if it's the right tool for the purpose.
Yes, the kernel "perf" tool.
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!