Bug 323740 - [Regression] Kontact/KMail starts eating one CPU when selecting a mail
Summary: [Regression] Kontact/KMail starts eating one CPU when selecting a mail
Status: RESOLVED DUPLICATE of bug 322958
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-19 17:25 UTC by Rolf Eike Beer
Modified: 2013-08-20 17:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eike Beer 2013-08-19 17:25:18 UTC
I just upgraded my machine from SC 4.10.5 to 4.11. I'm using KMail-part in Kontact with an (online) IMAP account.

After startup, once the first mail is selected, Kontact starts blocking one CPU (~20% on my Quadcore machine), akonadiserver usually uses the rest so both sum up to ~25% load. When in this state I can select some other mail but only get a message "please wait while fetching contents of this folder". I also can't send any mail during this. Kontact isn't entirely locked up, e.g. I can navigate through the menu and the like. So I guess it is in some sort of loop talking to akonadi and getting flooded with replies so the event loop is always busy.

Since I can easily reproduce this I can get you any sort of log/strace, but please tell me what to look for.

Reproducible: Always
Comment 1 Skander Morgenthaler 2013-08-19 21:23:01 UTC
Same problem here, using gentoo x86_64, kde 4.11, qt 4.8.5, gcc-4.7.3 and maildir ressources (fetching mails via pop3). 

I can read about one or two mails with enough patience (5-15 Minutes of waiting), after that kmail needs forever (>1h) to display the next message. If I can help by providing more information, please let me know.
Comment 2 Rolf Eike Beer 2013-08-19 21:51:27 UTC
One more thing that I observed: if I quit kontact it will not go away, but hang around. It then uses less CPU time, but akonadi then uses more (numbers are something like 4% kontact 21% akonadi), so I think there is still the same communication going on in the background. When I then send send a term signal to kontact it really quits and akonadi immediately calms down.
Comment 3 David Faure 2013-08-20 08:34:59 UTC
Enable the job tracker in akonadiconsole, then start kmail, and watch which job takes a very long time to run.
Comment 4 Frederik Gladhorn 2013-08-20 09:56:54 UTC
I have the same symptoms - on a laptop everythig works fine, but on a machine using exchange-imap nothing seems to work. (well, it takes ages to open a mail).

On the shell I get this debug output (continously, all the time the same messages):
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting changed for "akonadi_maildir_resource_1"
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting changed for "akonadi_maildir_resource_1"
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting changed for "akonadi_maildir_resource_1"
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting changed for "akonadi_maildir_resource_1"
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting changed for "akonadi_maildir_resource_1"
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting changed for "akonadi_maildir_resource_1"
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.
Comment 5 Daniel Vrátil 2013-08-20 11:18:14 UTC
Frederik, you problem might be related to https://bugs.kde.org/show_bug.cgi?id=322958
Comment 6 Frederik Gladhorn 2013-08-20 13:03:55 UTC
Thanks Daniel!!!
So it is fixed for me as soon as I deleted a second "outbox" of the empty "local folders" account.
I had one outbox in English, the other one in Norwegian, so I guess changing languages has the potential to mess things up by creating duplicate special folders.
Now I have kmail working at great speeds again :)
Comment 7 Rolf Eike Beer 2013-08-20 17:13:50 UTC
Confirmed to be dupe, deleting duplicate outbox fixed the issue.

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