Bug 309732

Summary: memory leak in kmail and virtuoso
Product: [Applications] kmail2 Reporter: Martin Tlustos <martin.tlustos>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: smartins
Priority: NOR    
Version: 4.9.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Martin Tlustos 2012-11-08 08:14:33 UTC 
after stopping nepomuk services and re-enabling them, kmail and virtuoso start to eat up memory (kmail both extra and within kontact). Virtuose takes twice the size I set it to (will file an extra bug report on that), kmail slowly keeps on rising in memory usage every time I switch folders, open a new email, write or the like. It starts around 23MB and rose to over 120MB, if embedded in kontact, it rose to over 220MB before I ended it.

Reproducible: Always

Steps to Reproduce:
1. start kmail
2. work
3. see memory usage rise
Actual Results:  
memory usage rises slowly

Expected Results:  
should stop after some time. Some growth is normal, but not that much.

It probably mainly is a problem with nepomuk (surprise, surprise!), as I started to see this behaviour after I stopped and re-enabled nepomuk services.
Comment 1 Sergio Martins 2013-06-28 17:19:49 UTC 
Around 100mb is OK for Kmail.
How much is virtuoso taking ?
Comment 2 Sergio Martins 2013-07-18 09:12:04 UTC 
Git commit 815957a4a9ae567f271453aac222abf4c09900f9 by Sergio Martins.
Committed on 17/07/2013 at 09:45.
Pushed by smartins into branch 'KDE/4.11'.

mixedmaildir: don't use 1.5GB of memory when importing a very big folder

Subjobs pile up too fast because they are cheap to create and
because it's taking around 5 event loops for one to start.
Related: bug 260647, bug 317122, bug 307066, bug 295651

M  +41   -6    resources/mixedmaildir/retrieveitemsjob.cpp
M  +4    -2    resources/mixedmaildir/retrieveitemsjob.h

http://commits.kde.org/kdepim-runtime/815957a4a9ae567f271453aac222abf4c09900f9
Comment 3 Martin Tlustos 2014-05-08 15:24:01 UTC 
seems to work now. Mark as fixed