Bug 289920

Summary:	Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Filip Miletic <filmil>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	ccurtis0+kdebts, don-redhat, kde, Kicer86
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Filip Miletic 2011-12-27 12:44:04 UTC

Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

More details here: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/909022

On every KDE session startup, a bunch of akonadi-related processes are started. These start hogging the system CPU and RAM shortly after startup, and quickly tie up 100% CPU and 200% RAM (i.e. they use up almost 8G physical RAM and start chewing on swap as well!)

In order not to have my 2-core 8G RAM machine completely bogged down by these processes, I have to kill the processes manually, else my session becomes unusable and I have to reset the machine.

Ubuntu: up-to-date 11.10


Reproducible: Always

Steps to Reproduce:
Log into a KDE session.

Actual Results:  
akonadi ties up all system resources up.

Expected Results:  
akonadi should not hog CPU nor RAM.

Comment 1 Christophe Marin 2011-12-27 13:45:26 UTC

paste the output of 'akonadictl --version' please

Comment 2 Filip Miletic 2011-12-27 17:30:18 UTC

$ akonadictl --version
Akonadi 1.6.2

Comment 3 Don Cohen 2012-01-17 21:47:30 UTC

I just updated to fedora kernel 3.1.9-1.fc16.x86_64, rebooted and found akonadiserver, mysql, akonadi_maildispatcher_agent using all of the cpu.
Even killing them didn't help - they restarted automatically.
I finally did 
 mv /usr/bin/akonadiserver /usr/bin/akonadiserverxxx
and then killed it.
Now what?
$ akonadictl --version
Akonadi 1.6.2

Why do I want to run any of this stuff anyway?
How can I permanently disable it (even better uninstall) in fedora 16?

Comment 4 Roman Fietze 2014-06-30 19:51:07 UTC

Still present in KDE/akonadi 4.13.2.

Comment 5 Michał Walenciak 2014-10-11 22:58:10 UTC

same here on Akonadi 1.13.0

Comment 6 Denis Kurz 2016-09-24 20:43:48 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 7 Denis Kurz 2017-01-07 21:48:56 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.