https://bugs.kde.org/show_bug.cgi?id=374780

            Bug ID: 374780
           Summary: Huge memory usage just for the calendar with korgac
                    and ical resource
           Product: korganizer
           Version: 5.2.3
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: korganizer-de...@kde.org
          Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Reopened bug #329205 :
"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"

The problem is still present in v5.2.3, to a lesser extent, but korganizer/pim
still uses way too much memory for not shown tasks/events, etc.

Updated grep commands :
`» grep BEGIN:VTODO calendrier.ics | wc -l
8553
» grep BEGIN:VJOURNAL calendrier.ics | wc -l
10
» grep BEGIN:VEVENT calendrier.ics | wc -l
5114
» grep BEGIN:JOURNAL calendrier.ics | wc -l 
0
» grep BEGIN:TODO calendrier.ics | wc -l    
0
» grep BEGIN:EVENT calendrier.ics | wc -l   
0`

Memory usage :
korganizer : 209 Mio
korgac     : 102 Mio
akonadi_ical_resource : 142 Mio
Total : 453 Mio of memory used...for a 6.6 Mio ics file.

Just to put that into perspective, that *68* time the size of the file on
disk!!


If you ask yourself why the numbers of events/tasks did not go up since 2013,
it's because the critical breaking bugs reported here are still present and
still prevents the normal use of Korganizer.

I do think Korganizer can revive from its ashes and get back the pre-2013
version functionalities, hence my recent testing here..

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to