Bug 286310 - Memory leak in akonadi_nepomuk_email_feeder. Eats all RAM and SWAP until it crashes
Summary: Memory leak in akonadi_nepomuk_email_feeder. Eats all RAM and SWAP until it c...
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.7
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-11 00:35 UTC by Aitor
Modified: 2011-12-04 11:41 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
akonadi_nepomuk_email_feeder Screenshot (82.45 KB, image/png)
2011-11-11 00:35 UTC, Aitor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aitor 2011-11-11 00:35:45 UTC
Created attachment 65503 [details]
akonadi_nepomuk_email_feeder Screenshot

Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

akonadi_nepomuk_email_feeder crashes (or has to be killed) twice (I have 4 IMAP accounts configured) before it stops being respawned.

Reproducible: Always

Steps to Reproduce:
Log into your account (kmail runs on logon) and see how akonadi_nepomuk_email_feeder eats all your ram.


Actual Results:  
akonadi_nepomuk_email_feeder eats all your ram until it crashes

Expected Results:  
it runs on background not being noticed
Comment 1 Aitor 2011-11-11 00:37:06 UTC
I'm open to provide more info this weekend if you can point me where to look ;)
Comment 2 Alejandro Nova 2011-11-12 05:26:11 UTC
This is the last great Nepomuk memory issue. In my system, dbus gets a significant impact also, so this could be a near-duplicate of the already fixed Nepomuk memory leaks. Sebastian, can you check if dbus calls are getting stuck with akonadi_nepomuk_email_feeder?

Also, what's the situation with KDE 4.8? AFAIK, akonadi_nepomuk_email_feeder was entirely rewritten.
Comment 3 Alejandro Nova 2011-11-12 06:00:23 UTC
@Aitor: A better workaround: try to delete the Nepomuk EMail Feeder from Akonadi Console. Run akonadiconsole in a command line, or look for Akonadi Console.
Comment 4 Will Stephenson 2011-11-18 23:24:45 UTC
I also get the leak with 4.8. kdepim reckon it's the resource passing items to the feeder faster than it can index them, so the queue grows.  I have a lot of RAM so it didn't OOM yet.
Comment 5 jos poortvliet 2011-11-21 23:35:12 UTC
The best way to 'work around this' is letting the feeder index all mail. This will of course get you a problem as it keeps growing :D

My solution was to schedule a large number of "akonadictl restart" over night.

Like this:

sleep 20m && akonadictl restart & sleep 40m && akonadictl restart & sleep 1h && akonadictl restart & sleep 1h && sleep 20m && akonadictl restart &

and so on. I bet there is a way better way of doing this but this allowed the feeder to index all my mail during one night and now the problem is solved so I'm happy :D
Comment 6 Alejandro Nova 2011-11-27 05:04:30 UTC
Can you upgrade shared-desktop-ontologies and retest?
Comment 7 Aitor 2011-11-27 12:53:26 UTC
@Alejandro Nova Deleteing Nepomuk EMail Feeder was not useful for me as it was recreated automatically upon restart.
Comment 8 Aitor 2011-11-27 18:14:24 UTC
I've just upgraded to shared-desktop-ontologies 0.8.1 and I haven't notice any change. I still need to kill akonadi_nepomuk_email_feeder processes
Comment 9 Alejandro Nova 2011-11-28 00:58:09 UTC
@Aitor: Can you do a final test with s-d-o 0.8.1 or a git snapshot, and KDE 4.8 Beta 1? With that combination, I do not get any memory leak indexing mails. I even recreated my Nepomuk database and the akonadi-nepomuk-feeder didn't grow beyond 120 MB.
Comment 10 Aitor 2011-12-03 22:05:06 UTC
I've just upgraded to KDE 4.8 Beta 1 and I can not reproduce this any more.