Bug 408975 - Starting the dashboard makes plasmashell spin up CPU cores
Summary: Starting the dashboard makes plasmashell spin up CPU cores
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeplasma-addons
Classification: Plasma
Component: Application Dashboard (show other bugs)
Version: 5.16.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-21 07:56 UTC by Philipp A.
Modified: 2022-07-14 07:55 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp A. 2019-06-21 07:56:54 UTC 
Having the application dashboard on my desktop/panel or starting it with

plasmawindowed org.kde.plasma.kickerdash

… causes ~70% CPU load from the processes kactivitymanagerd and plasmashell on changing cores. With “changing”, I mean that every half second or so, another core spins up.

This behavior continues after I remove the application dashboard or close the plasmawindowed window.
Comment 1 Philipp A. 2019-06-21 08:19:37 UTC 
Oh, and that makes plasmashell super unresponsive. Hover effects have more than a second delay, and processing notifications also takes a while (they appear unresponsively and need time to move to their intended position and become responsive)
Comment 2 Philipp A. 2022-07-14 07:55:19 UTC 
Seems like it was resolved