Created attachment 160642 [details] CPU load before killing akonadi SUMMARY When running idle I've noticed that recently, after a few upgrades in QT/plasma packages, my CPU fan was blowing faster than before. The CPU monitor showed me that there was a permanent CPU load of 25% which wasn't there before. After investigating, I found the culprit : akonadi and all its tasks where busying my system, even after several hours, while all the processing of startup, mails reception, had already been done. File indexing is deactivated on my system. STEPS TO REPRODUCE 1. Log in a session that has kmail configured with a few accounts and wait a few minutes 2. Look at the CPU monitor OBSERVED RESULT The CPU load is way too high... EXPECTED RESULT The CPU load should be around 1 or 2 %... SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.4.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz Memory: 31.2 Gio of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics 650 Manufacturer: Intel Corporation Product Name: NUC7i7BNH System Version: J31153-308 ADDITIONAL INFORMATION I've taken a few screenshots and `ps aux` outputs...
Created attachment 160643 [details] List of akonadi processes before killing them
Created attachment 160644 [details] System monitor displaying akonadi It's in french... "Rappels d'agenda" means "Agenda Reminder" (something like that).
Created attachment 160645 [details] How I kill akonadi I just click on "Close an application" (in red).
Created attachment 160646 [details] CPU load a few seconds after killing akonadi
Created attachment 160647 [details] Normal CPU load after killing akonadi.
Obviously, when I start KMail after, it asks to restart akonadi... And there it is again, taking up to 25% CPU...
Hum. In fine, it wasn't akonadi but KMail. Killing kmail stops the CPU hog while akonadi keeps working.
A new upgrade in testing resolved the issue...