Right now, when opening a folder a populating the message list, all headers of the messages are fetched and put into a KMime::Message object. This is way too expensive, and will show as speed, disk space and memory problems. Instead, only the headers that are really needed should be cached and loaded, which are those displayed in the message list. And there shouldn't be a big KMime::Message object for each of those, but some more memory efficient structure. Same goes for the cache in Akonadi, it should not store the complete header in plain text there. In the same vein, the IMAP resource should not fetch the complete header, but only the needed header fields, which is possible with the IMAP protocol (and e.g. tinymail does that). This needs to be fixed at several levels, not just KMail.
*** Bug 233138 has been marked as a duplicate of this bug. ***
Hej, this should be fixed now. Can you reproduce? Ciao, Tobias
> this should be fixed now. Can you reproduce? AFAIK the messagelist still loads a KMime::Message object for each item, and the server sends the complete header instead of only the fields that are needed. The message list stores a tree of MessageItem's, and MessageItem::Private contains the complete Akonadi::Item, which includes the KMime::Message object. On the Akonadi server, we store the complete header in the cache as well, which is also a waste of space and bandwidth.
As far as I can see the Problem still exists in 4.7RC1. Loading the Messages in my local folders (archive) immediately results in a very much increased memory usage of akonadi_mixedmaildir_resource (from 16MiB to 430). When browsing my DIMAP-Folders nothing of the sort happens.
This is affecting me too. After starting kontact akonadi_mixedmaildir_resource memory usage goes up to over 2G.
(In reply to comment #5) > This is affecting me too. > After starting kontact akonadi_mixedmaildir_resource memory usage goes up to > over 2G. That's bug 260647, which has a patch in review
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 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.