Akonadi acting up (again)

Kevin Krammer krammer at kde.org
Mon Sep 16 10:38:40 BST 2013

Hi Frank,

On Monday, 2013-09-16, Frank Steinmetzger wrote:

> On another machine I had the same symptoms at first, but then it behaved
> again. But that was a 32 bit system.  On my current main 64 bit machine,
> it just isn't happening. Akonadi has been clogging the CPU for 20
> minutes now. Closing the KMail or Kontakt window doesn't help, the CPU
> load is still there. I have to kill the KMail/Kontact process which
> still lingers in the background, only then will Akonadi return to being
> quiet.

That sounds a lot like the problem being in KMail or in something that KMail 
It not exiting on quit is a hint that there is some active action inside it 
that inhibit application exit, e.g. some long running job.
Also, the fact that killing it stops the observed CPU usage again suggests 
that it is the origin of the load.

I am not sure how best to check what it is doing right there.
One thing you could try is to run akonadiconsole before launching KMail and 
then check the Job Tracker tab when the high usage occurs and look which type 
of job is reported as running for KMail.


Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde/attachments/20130916/561e3edc/attachment.sig>
-------------- next part --------------
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

More information about the kde mailing list