[Bug 294772] Akonadi IMAP/maildir resource agent writes extensively for long period after deleting a several thousand e-mails

[Christian Burger]

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

Christian Burger <christian.burger at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.7                         |4.8

--- Comment #2 from Christian Burger <christian.burger at gmail.com> ---
Sorry, took my computer some time to build that on an old Pentium 4. :)

I can now verify that the problem still exists in 4.8 and Akonadi 1.7.

Addionally, I just saw, that the file
agent_config_akonadi_nepomuk_feeder_changes.dat
shows the same behaviour, but grows in size. I assume the not-shrinking is to
blame to the fact, that I have Nepomuk deactivated and so no one is on the
receiving end. Its about 6.5 megabytes by now. I think it's growing with every
change to my mail directories. Probably another bug, which I will file as soon
as this one is resolved for me.

I observed an interessting fact: The problem only occurs if I move around or
copy mail within Kontact. If a big pile of mail is introduced from the IMAP
server, the relevant Akonadi agent keeps quiet and just the nepomuk agent
starts acting up. I will attach two new strace outputs from an IMAP resource
process, both compressed with XZ again.

PS: During a move of mail folder Kontact crashed and afterwards the mail folder
at the old position was gone, at the new position it was empty and then the new
empty folder  disappeared into thin air after I checked my mail in the account
containing the new folder. I begin to understand why some people say KMail2 is
problematic to say the least. This would probably not have happened with
KMail1, where all mail is backed up by a maildir folder and there was no
"complex" Akonadi metadata scheme sandwiched inbetween.

Don't worry I will bear with you. So, what do you need from me?

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