Bug 348764 - System monitor plasma widgets cause 100% cpu load
Summary: System monitor plasma widgets cause 100% cpu load
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Monitor (show other bugs)
Version: 5.5.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-06 00:03 UTC by slartibart70
Modified: 2017-01-13 10:22 UTC (History)
3 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 slartibart70 2015-06-06 00:03:11 UTC
very simple:
add 'cpu load monitor' or 'network monitor' or 'memory status' to the desktop.
No need to resize or reposition, just wait a few seconds.
The CPU load of the system goes up to 100%

(other widgets do not show this behaviour)

Reproducible: Always
Comment 1 Christian 2015-06-08 20:00:10 UTC
Well, *I confirm that*, and add one more: 

The Instant messaging "notification widget" can also use a 100% of one CPU core: if you add an account with a wrong password, it tries to reconnect and that start the "connecting" circle animation consumming 100% of one core.

I think that when someone messages you, the envelop animation can also consume a lot of CPU.
Comment 2 Christian 2015-06-08 20:04:26 UTC
Worth to say that I switched off the IM checkbox at the systray preferences and CPU restores to its tipical use.

If you switch on again, you'll have the plasmashell consumming 100% of CPU again.
Comment 3 kolAflash 2016-11-22 13:10:00 UTC
Maybe duplicate: bug 345696

Maybe related:
bug 352813
bug 359890
bug 364061
Comment 4 David Edmundson 2017-01-13 10:22:04 UTC
high CPU

Thanks, but this isn't very helpful on it's own, so I'm going to close this, but please see the linked reports.

We have multiple high CPU bugs, some caused by us, some not, some fixed, some unknown. It's hard to say what the cause of each one is, and bug reports get convuluted.

I've made a list of some of the bigger more specific ones:

For high CPU caused by reloading icons over the SNI protocols see:
356479

For high CPU caused by infinite spurious X events see:
373368

For others, search other bug reports here.