At all time, I have 1 GiB of memory used by korganizer, korgac and akonadi_ical_resource processes, and only 72 MiB of it is shared. The main memory hog seems to come from a duplication between the korganizer and korgac processes, respectively with 487 and 469 MiB used. Here is my memory consumption using 4.11.2 : Process | Memory | Shared memory | Virtual Memory korganizer | 487.7 M | 31.0 M | 1.2 G akonadi_ical_resource_1 | 5.0 M | 12.7 M | 308.4 M akonadi_ical_resource_2 | 126.7 M | 13.5 M | 448.6 M ==> korgac | 469.0 M | 15.1 M | 1.0 G <== The total memory usage for a single calendar is in my humble opinion far too high (more than 1,088 GiB) for a 6.7 MiB ics file. This is specially true for netbook users. More history about this bug can be found in bug 314900. Reproducible: Always
grep BEGIN:VEVENT your.ical | wc -l grep BEGIN:JOURNAL your.ical | wc -l grep BEGIN:TODO your.ical | wc -l What's the output of these 3 commands ?
$ grep BEGIN:VEVENT calendrier.ics | wc -l 5273 $ grep BEGIN:VJOURNAL calendrier.ics | wc -l 10 $ grep BEGIN:VTODO calendrier.ics | wc -l 8757 (there is no BEGIN:JOURNAL nor BEGIN:TODO strings in that ics file)
Why does it say you have 8757 todo's then ?
Because Alexandre grep'ed for BEGIN:VTODO, not BEGIN:TODO.
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.
To be continued on #374780