Bug 293354 - memory leak with remote ics calendar
Summary: memory leak with remote ics calendar
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: korgac
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-05 11:53 UTC by Silver Salonen
Modified: 2014-05-25 11:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
korgac log file (201.61 KB, text/x-log)
2012-02-06 10:07 UTC, Silver Salonen 		Details
korgac log file (43.04 KB, application/zip)
2012-02-06 10:08 UTC, Silver Salonen 		Details
korgac valgrind log (154.77 KB, application/x-gzip)
2014-05-22 17:51 UTC, Hussam Al-Tayeb 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Silver Salonen 2012-02-05 11:53:12 UTC 
Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

I added a new remote calendar and now korgac + akonadi feeder processes start eating up memory once korgac has been started (even though I don't do anything with calendars). They each take about 1GB RAM in a few hours.

Reproducible: Always

Steps to Reproduce:
1) Add remote ICS calendar
2) Start korgac
3) Wait and observe memory usage of korgac

Actual Results:  
Memory usage increases

Expected Results:  
Memory usage stays the same
Comment 1 Sergio Martins 2012-02-05 20:09:42 UTC 
I can't reproduce here.

please run korgac with:
valgrind --leak-check=yes korgac --nofork &> valgrind.log

and attach valgrind.log here.

Be sure to be using debug symbols
Comment 2 Silver Salonen 2012-02-06 10:07:18 UTC 
Created attachment 68549 [details]
korgac log file

BTW, the akonadi process eating as much RAM is 'akonadi_kcal_resource'.
Comment 3 Silver Salonen 2012-02-06 10:08:57 UTC 
Created attachment 68550 [details]
korgac log file

Log file after ctrl+c
Comment 4 Sergio Martins 2012-02-06 20:21:32 UTC 
(In reply to comment #2)
> Created an attachment (id=68549) [details]
> korgac log file
> 
> BTW, the akonadi process eating as much RAM is 'akonadi_kcal_resource'.

The akonadi_kcal_resource is so you can use legacy ( kresources ) resources with akonadi.

Can you try with a pure akonadi resource? akonadi_ical_resource
Comment 5 Silver Salonen 2012-02-07 11:28:17 UTC 
This is quite obscure. If I add "traditional KDE calendar", it means the legacy resource? And if I add ICS calendar, it means akonadi_ical_resource?

I think I hit some other bug(s) here:
  1) If I add remote ICS calendar under Akonadi resources, first the wizard does not pop up
  2) If I open the configuration dialog manually and configure it, the calendar is not shown in KOrganizer.
  3) If I add remote ICS in KOrganizer, nothing happens - no configuring dialog is opened.
  4) The resource was still added under resources, so I could configure it, but it is still not shown in KOrganizer.
Comment 6 Silver Salonen 2012-02-07 15:49:49 UTC 
OK, the remote ICS calendar appeared after restarting maching (logging out and in did not have any effect). Memory usage is stable now.

BTW, along with korgac and akonadi_kcal_resource, also memory usage of plasma-desktop increased as much.

So anyway, this bug seems related to akonadi_kcal_resource/kresource indeed.
Comment 7 Hussam Al-Tayeb 2013-12-01 21:45:59 UTC 
still happens here with kde 4.11.3
Comment 8 Hussam Al-Tayeb 2014-05-22 15:35:42 UTC 
still happens with kde 4.13.1
I will upload a valgrind log sometime this weekend.
Comment 9 Hussam Al-Tayeb 2014-05-22 17:51:22 UTC 
Created attachment 86773 [details]
korgac valgrind log
Comment 10 Sergio Martins 2014-05-25 11:02:56 UTC 
(In reply to comment #9)
> Created attachment 86773 [details]
> korgac valgrind log

Can you instead use callgrind on it ?