memory consumption grows while filtering, but doesn't decrease when finished it only grows till stand still Reproducible: Always Steps to Reproduce: 1.select some hundred mails 2.press CTRL-J for filtering 3.watch mem consumption of proc mail_filter_agent Expected Results: patch
I've just been hit by this. Created a new filter, selected a folder and applied it on it (directly in the filter creation dialog). When it finished, akonadi_mail_filter consumed 16% of my 2GB of RAM (according to htop), which hurts. This didn't go down within five minutes, so I restarted akonadi. using KDE 4.9.98 on Chakra.
so it increases each time that you filter ? or it stays at 16% ?
Reapplying the same filter : stayed at 16% Creating and applying new filter (after running first one) : went up to 33% Couldn't try much else, since by that time the laptop became unusable...
ah each time you create a new filter and click apply it it increases ? I didn't test. Will do
Please see http://sourceware.org/bugzilla/show_bug.cgi?id=14827 and comment there
@developers: please check code in mail filter agent for logging feature(s) !!! I noticed by a fault in my filter rules that: the less filters kmail processes the less memory it allocates looking for the filter logs I saw that filter logging was enabled by default to unlimited by disabling filter logging I could decrease memory consumption very significantly and increase filter speed many times but: memory consumption is still increasing !!! even not that much than before so ther must be a memory leak ......... before, with filter logging enabled, I could process some hundred mails till memory usage of filter agent reached about 1.5GB one core was equipped with nothing but the filteragent but nothing happened any more and I had to restart filter_agent now with the filter logging disabled kmail could handle about 15000 mails and memory consumption raised only from 14M up to below 250M greets, peter OS12.3RC1 KDE4.10
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.