Bug 194238 - Akonadi server going high on cpu usage
Summary: Akonadi server going high on cpu usage
Status: RESOLVED DUPLICATE of bug 193249
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: server (show other bugs)
Version: 4.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-27 00:05 UTC by Steffen Schloenvoigt
Modified: 2009-05-27 00:20 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Schloenvoigt 2009-05-27 00:05:48 UTC
Version:            (using KDE 4.2.85)
OS:                Linux
Installed from:    SuSE RPMs

Hi.

Since migration to KDE 4.3 beta 1 (4.2.85) akonadiserver is going crazy on cpu usage as soon as one of the following applications is running:
* krunner
* kopete
* kontact / korgac

When starting the server with akonadictl start, the following output is returned repeatedly:

[akonadiserver] posting retrieval request for item 34
[akonadiserver] processRequest() - current thread: Akonadi::ItemRetrievalThread(0x80ce170)  retrieval thread: Akonadi::ItemRetrievalThread(0x80ce170)
[akonadiserver] processing retrieval request for item 34  parts: ("RFC822")
[akonadiserver] checking if request for item 34 has been processed...
[akonadiserver] request for item 34 still pending - waiting
[akonadiserver] STORE: handling command:  "REMOTEID"
[akonadiserver] STORE: handling command:  "PLD:RFC822"
[akonadiserver] continuing
[akonadiserver] checking if request for item 34 has been processed...
[akonadiserver] request for item 34 processed, error: ""
[akonadiserver] requestItemDelivery() - current thread: Akonadi::AkonadiConnection(0x8190a28)  retrieval thread: Akonadi::ItemRetrievalThread(0x80ce170)

Thereby changing the number (here 34). As more of the above mentioned applications run, as more message sequences like this are put out (All ening in error "" ???).

Kind regards,
Steffen
Comment 1 Christophe Marin 2009-05-27 00:20:59 UTC

*** This bug has been marked as a duplicate of bug 193249 ***