Created attachment 112200 [details] perf record --call-graph dwarf /usr/bin/plasmashell even laptop fans kick up after a while. ~15% constant cpu use while idling on average
Note sure if the exact same issue : I was also having ridiculous cpu usage with plasma (30% on all cores). Upon closer inspection, I noticed a few coredumps in HTOP. Looking at coredumpctl -r list , it was filled with : Tue 2018-04-24 14:13:32 JST 14647 1000 1001 6 present /usr/bin/kactivitymanagerd About three per second ! pkill -f kactivitymanagerd stopped the coredumps and high cpu usage.
(In reply to UberPanda from comment #1) > Note sure if the exact same issue : > I was also having ridiculous cpu usage with plasma (30% on all cores). Upon > closer inspection, I noticed a few coredumps in HTOP. > > Looking at coredumpctl -r list , it was filled with : > > Tue 2018-04-24 14:13:32 JST 14647 1000 1001 6 present > /usr/bin/kactivitymanagerd > > About three per second ! > > pkill -f kactivitymanagerd stopped the coredumps and high cpu usage. Forgot to mention : HD4600 GPU with intel i7 4600M on manjaro KDE with kernel 4.14 and xf86-video-amdgpu drivers
(In reply to UberPanda from comment #1) > pkill -f kactivitymanagerd stopped the coredumps and high cpu usage. Running it slighty reduces cpu usage and then it goes back to the normal ~15 - 30% wilst idling because kactivitymanagerd just respawns or at least I can constantly kill it with pkill without it telling me it is not running.
Created attachment 112208 [details] First screenshot of blinking activity settings
Created attachment 112209 [details] Second screenshot of blinking activity settings
(In reply to Zakhar from comment #3) > (In reply to UberPanda from comment #1) > > pkill -f kactivitymanagerd stopped the coredumps and high cpu usage. > > Running it slighty reduces cpu usage and then it goes back to the normal ~15 > - 30% wilst idling because kactivitymanagerd just respawns or at least I can > constantly kill it with pkill without it telling me it is not running. Mine does not restart. However, I noticed that when launching the activity settings through the application launcher, kactivitymanagerd is back and the window is error blinking (see attached screenshot). My guess is something is really broken with the activity manager.
I should add this problem existed in the last stable release pre 5.45.0 however cpu usage was not as high as it is with this revision. I should mention the new revision plugged some serious memory leaks but unfortunately didn't address the cpu usage.
What Qt version?
(In reply to David Edmundson from comment #8) > What Qt version? 5.10.1-1 in my case
Qt 5.9.5
I think I found a way to brute force a fix : In systemctl, the error boils down to : KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory I just entirely deleted .local/share/kactivitymanagerd/resources/ and rebooted. The bug did not reappear afterwards (it's been an hour now).
I've tried to reproduce this issue but my Plasma sits at 0% idle. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
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!