To clarify, out of the box on krillin with no calendar sync even enabled, evolution-calendar-factory uses 32MB which is the 4th highest process in memory usage. This is with an empty database of no calendar events or alarms.
I'm assuming evolution-calendar-factory gets loaded by indicator- datetime initially such that the indicator can show calendar events. If you have a large database of calendar entries (i.e. after you've done a google calendar sync), as Pat reported this process can grow to well over 100MB. It seems to have no upper bound, and since the evolution backend for calendar is simply a flat file of type .ics, e-c-f appears to load the entire file into memory. e-c-f really needs a sqlite backend or something such that it can manage it more efficiently. Someone needs to investigate what can be done in the short term reduce the memory usage if possible. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage Status in “evolution-data-server” package in Ubuntu: New Status in “indicator-datetime” package in Ubuntu: New Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1342123/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
