Bug 329205

Summary: Huge memory usage just for the calendar with korgac and ical resource
Product: [Frameworks and Libraries] Akonadi Reporter: Alexandre Bonneau <alexandre.bonneau>
Component: ICal file resourceAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: smartins
Priority: NOR    
Version: 4.11   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alexandre Bonneau 2013-12-24 16:19:08 UTC 
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
Comment 1 Sergio Martins 2013-12-24 22:06:15 UTC 
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 ?
Comment 2 Alexandre Bonneau 2013-12-26 00:27:47 UTC 
$ 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)
Comment 3 Sergio Martins 2013-12-26 23:21:22 UTC 
Why does it say you have 8757 todo's then ?
Comment 4 Christoph Feck 2013-12-27 01:08:41 UTC 
Because Alexandre grep'ed for BEGIN:VTODO, not BEGIN:TODO.
Comment 5 Denis Kurz 2016-09-24 20:33:20 UTC 
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.
Comment 6 Denis Kurz 2017-01-07 22:43:40 UTC 
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.
Comment 7 Alexandre Bonneau 2017-01-08 20:28:18 UTC 
To be continued on #374780