Bug 407526 - Plasmashell and ksysguardd uses cpu
Summary: Plasmashell and ksysguardd uses cpu
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.15.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-14 14:45 UTC by r0ck3r
Modified: 2019-12-09 20:25 UTC (History)
4 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 r0ck3r 2019-05-14 14:45:10 UTC
SUMMARY
After some uptime plasma is using 100% one of my CPU cores. After killing plasmashell and rerun it - CPU usage goes normal, but after some time it happens again. Killing ksysguardd fixes this problem too, but it happens again too
STEPS TO REPRODUCE
1. Add next widgets to your desktop: cpu usage, ram usage, disk usage, disk io
2. Wait for some hours

OBSERVED RESULT
In your CPU usage widget you will see, that cpu usage is big and plasma works very slow


EXPECTED RESULT
Stable work, without abnormally cpu usage


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 30
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.1
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile
Comment 1 David Edmundson 2019-08-26 09:18:44 UTC
>1. Add next widgets to your desktop: cpu usage, ram usage, disk usage, disk io

Could you try to narrow down which one(s) make an impact
Comment 2 Jiri Palecek 2019-08-31 02:28:50 UTC
I was having similar problems on my computer, turns out it was caused by one mount point mentioned twice in mtab.

I created some patches addressing this, could you have a look at them (and perhaps test them) here: https://phabricator.kde.org/T11473

It may be the case that your problems are different than what I was having, in that case, if you can reproduce it, a strace of plasmashell would be handy.
Comment 3 Bug Janitor Service 2019-09-15 04:33:08 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 4 Bug Janitor Service 2019-09-30 04:33:08 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!