<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>323740</bug_id>
          
          <creation_ts>2013-08-19 17:25:18 +0000</creation_ts>
          <short_desc>[Regression] Kontact/KMail starts eating one CPU when selecting a mail</short_desc>
          <delta_ts>2013-08-20 17:13:50 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>2</classification_id>
          <classification>Applications</classification>
          <product>kmail2</product>
          <component>general</component>
          <version>4.11</version>
          <rep_platform>openSUSE</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>322958</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Rolf Eike Beer">kde</reporter>
          <assigned_to name="kdepim bugs">pim-bugs-null</assigned_to>
          <cc>dvratil</cc>
    
    <cc>gladhorn</cc>
    
    <cc>smorg</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1391011</commentid>
    <comment_count>0</comment_count>
    <who name="Rolf Eike Beer">kde</who>
    <bug_when>2013-08-19 17:25:18 +0000</bug_when>
    <thetext>I just upgraded my machine from SC 4.10.5 to 4.11. I&apos;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 &quot;please wait while fetching contents of this folder&quot;. I also can&apos;t send any mail during this. Kontact isn&apos;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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391067</commentid>
    <comment_count>1</comment_count>
    <who name="Skander Morgenthaler">smorg</who>
    <bug_when>2013-08-19 21:23:01 +0000</bug_when>
    <thetext>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 (&gt;1h) to display the next message. If I can help by providing more information, please let me know.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391073</commentid>
    <comment_count>2</comment_count>
    <who name="Rolf Eike Beer">kde</who>
    <bug_when>2013-08-19 21:51:27 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391152</commentid>
    <comment_count>3</comment_count>
    <who name="David Faure">faure</who>
    <bug_when>2013-08-20 08:34:59 +0000</bug_when>
    <thetext>Enable the job tracker in akonadiconsole, then start kmail, and watch which job takes a very long time to run.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391164</commentid>
    <comment_count>4</comment_count>
    <who name="Frederik Gladhorn">gladhorn</who>
    <bug_when>2013-08-20 09:56:54 +0000</bug_when>
    <thetext>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 &quot;akonadi_maildir_resource_1&quot;
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 &quot;akonadi_maildir_resource_1&quot;
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 &quot;akonadi_maildir_resource_1&quot;
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 &quot;akonadi_maildir_resource_1&quot;
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 &quot;akonadi_maildir_resource_1&quot;
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 &quot;akonadi_maildir_resource_1&quot;
kmail2(23566)/libakonadi Akonadi::SpecialCollectionsPrivate::emitChanged: Emitting defaultFoldersChanged.
kmail2(23566) MailCommon::Kernel::initFolders: Initialized and looking for specialcollection folders.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391186</commentid>
    <comment_count>5</comment_count>
    <who name="Daniel Vrátil">dvratil</who>
    <bug_when>2013-08-20 11:18:14 +0000</bug_when>
    <thetext>Frederik, you problem might be related to https://bugs.kde.org/show_bug.cgi?id=322958</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391214</commentid>
    <comment_count>6</comment_count>
    <who name="Frederik Gladhorn">gladhorn</who>
    <bug_when>2013-08-20 13:03:55 +0000</bug_when>
    <thetext>Thanks Daniel!!!
So it is fixed for me as soon as I deleted a second &quot;outbox&quot; of the empty &quot;local folders&quot; 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 :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1391286</commentid>
    <comment_count>7</comment_count>
    <who name="Rolf Eike Beer">kde</who>
    <bug_when>2013-08-20 17:13:50 +0000</bug_when>
    <thetext>Confirmed to be dupe, deleting duplicate outbox fixed the issue.

*** This bug has been marked as a duplicate of bug 322958 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>