[kmail2] [Bug 316541] akonadi_imap_resource uses 50% of one core even while KMail is shut down

[kdebugzilla at gamblit.org]

https://bugs.kde.org/show_bug.cgi?id=316541

kdebugzilla at gamblit.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdebugzilla at gamblit.org

--- Comment #8 from kdebugzilla at gamblit.org ---
I've had this problem since I can remember. I'm not sure if I had it with KDE
3.x, but I'm SURE i've had it with EVERY version along KDE 4.x

The problem only happens with one specific IMAP account, which only accepts one
connection at a time. I've searched all over for a way to limit the number of
IMAP connections KMail/Akonadi initiates to a specific server, but it seems
there's no way to do it. I can't even delete email, or mark it as read, as all
changes are lost when then connection goes down. I have to do it all via
webmail.

Every once in a while, after a connection drop, the Akonadi process related to
this specific IMAP account starts consuming 100% of the CPU and, like someone
else already said, the only way to stop it is to restart Akonadi.

The server dropping the connection CAN lead to this problem, but not always.
Sometimes I just get all my deleted mail back, and my read mail marked as
unread. However, I also had a WiFi router problem where the connection appeared
to be up, but there was no connection to the network. If this happens
overnight, it triggers the Akonadi CPU usage bug 100% of the time.



My strace right now shows basically nothing although is has been running for
about 10 minutes now, but Akonadi is consuming 100% CPU:

[root at roadrunner ~]# strace -fp 16902
Process 16902 attached with 4 threads
[pid 12245] restart_syscall(<... resuming interrupted call ...> <unfinished
...>
[pid 17968] restart_syscall(<... resuming interrupted call ...> <unfinished
...>
[pid 16902] futex(0xcdea0c, FUTEX_WAIT_PRIVATE, 3, NULL

-- 
You are receiving this mail because:
You are the assignee for the bug.