I have eGroupware DAV resource in Akonadi. Its akonadi_davgroupware_resource process takes an increasing amount of memory over the time, even though I do nothing with it - KOrganizer just sits on the system tray. Current memory information fro System Monitor: Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings. Private 259224 KB [heap] 1088 KB /usr/lib64/libQtXmlPatterns.so.4.8.2 308 KB /usr/bin/akonadi_davgroupware_resource 228 KB /usr/lib64/libQtGui.so.4.8.2 124 KB /usr/lib64/libkdeui.so.5.8.0 Shared 3116 KB /usr/lib64/libQtGui.so.4.8.2 1344 KB /usr/lib64/libQtCore.so.4.8.2 928 KB /usr/lib64/libkdeui.so.5.8.0 768 KB /usr/lib64/libakonadi-kde.so.4.8.0 696 KB /usr/lib64/libkdecore.so.5.8.0 Totals Pixmap 785 KB (Might be stored in the graphics card's memory) Private 262132 KB (= 2096 KB clean + 260036 KB dirty) Shared 13612 KB (= 12964 KB clean + 648 KB dirty) Rss 275744 KB (= Private + Shared) Pss 264313 KB (= Private + Shared/Number of Processes) Swap 1712 KB Reproducible: Always Steps to Reproduce: 1. Add eGroupware resource into Akonadi 2. Start KOrganizer 3. Wait and watch the memory usage Actual Results: Memory usage increases over the time Expected Results: Memory usage should stay approximately the same
I am seeing something similar, but I'm not sure that it is a leak. I have four Google calendars that I sync with that are DAV groupware resources. During sync, the akonadi_davgroupware_resource process slowly eats up to ~230 MB memory. On successive syncs, the memory does not increase. I don't know if ~230 MB is normal for this kind of activity. How do you get that detailed memory usage per library?
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.