Bug 243829 - KMail2 takes all the cpu and too much time to process and group messages in an imap folder
Summary: KMail2 takes all the cpu and too much time to process and group messages in a...
Status: RESOLVED DUPLICATE of bug 244503
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 2.0.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks: 223438
  Show dependency treegraph
 
Reported: 2010-07-07 09:46 UTC by Stefano
Modified: 2010-07-22 12:40 UTC (History)
0 users

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 Stefano 2010-07-07 09:46:40 UTC
Version:           2.0 beta1 (using Devel) 
OS:                Linux

I have around 20 folders in my emai account, where the Inbox folder has ~25k emails (occupying ~6GB) while the other folders contain less messages (100 on average).

I did not use the migrator, as I started with a newly created user. I also disabled nepomuk in the system settings.

After launching kmail, I tried (by using the wizard) to create an online imap account (thus by not checking "download messages for offline use"). The synchronization was successful and now I can see all the emails in my folders. However, there are two annoying issues:

- processing and grouping emails is very slow and takes all my cpu. For instance, processing and grouping threads for my inbox takes around 10 seconds, while with kmail 4.4 (and disconnected imap account) took ~1 second.

- deleting messages in kmail does not delete emails from the imap server. Indeed, after some time, deleted messages re-appear in my folders.


Reproducible: Always

Steps to Reproduce:
Create an online imap account and use kmail2
Comment 1 Thomas McGuire 2010-07-22 12:40:31 UTC
Please, only one issue per bug report, for the deletion problem please file a separate report.
For slow folder opening, see bug 244503 (might need to be reopened)

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