Bug 353507 - plasmashell uses too much CPU when copying/moving/deleting files
Summary: plasmashell uses too much CPU when copying/moving/deleting files
Status: RESOLVED DUPLICATE of bug 378010
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.4.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Martin Klapetek
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-10-03 22:13 UTC by Najjar
Modified: 2018-12-14 15:43 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Najjar 2015-10-03 22:13:52 UTC
When doing file operations, plasmashell uses CPU as high as 15%. Such as copying or moving a file across any medium or type of FS.

I use Dolphin as a FM, and the bug happens with files on a Samba share, or files on a USB (regardless of the FS), or even within the same partition or different Linux partitions.

I've also noticed that it happens (~8% CPU) when playing a video file (I use VLC) after such file operation (the operation is done when this happens).

I think it might be the progress bar in notifications, but I'm not sure.

Reproducible: Always
Comment 1 David Edmundson 2015-10-03 23:40:55 UTC
Can I have the output of qdbus org.kde.KWin /KWin supportInformation
Comment 2 Najjar 2015-10-04 03:11:01 UTC
Here you go: https://paste.kde.org/p9lrdfyyt
Comment 3 Tomas Mecir 2015-10-26 18:47:18 UTC
Similar issue here, 100% cpu usage (one core) while that animation is playing.

Note that while I have an optimus laptop, the nvidia card is disabled via bbswitch and nouveau/nvidia drivers are not installed, so I doubt this is related to 351888.

https://paste.kde.org/pand8gcd2
Comment 4 Najjar 2016-03-18 03:03:47 UTC
This is still an issue in the latest stable (5.5.5)
Comment 5 Najjar 2016-08-31 14:11:26 UTC
So I came back here to report that the latest version (5.7.4) still uses way too much CPU.
I also saw bug 366060 from a month back marked as Resolved without any type of clarification by the closer, or by the assigned person (Edmundson). The report was on version 5.6.5
Comment 6 Andrew Crouthamel 2018-09-26 22:16:13 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 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!
Comment 7 Najjar 2018-09-27 20:24:01 UTC
(In reply to Andrew Crouthamel from comment #6)
> 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 Edmudnson has to look at the logs he's requested. WAITINGFORINFO isn't on our part. (I realize that this is probably an automated reply, but nonetheless)
Comment 8 Andrew Crouthamel 2018-09-27 20:28:50 UTC
Thanks for the update, I've set this to REPORTED so it won't be auto-closed.
Comment 9 Alexander Potashev 2018-11-07 01:20:43 UTC
May be related to bug #373368
Comment 10 David Edmundson 2018-12-14 15:43:10 UTC

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