desktop-packages team mailing list archive

[Jonathan Sahagun <1342123@xxxxxxxxxxxxxxxxxx>]

Small update:

> Bill Filler (bfiller) wrote on 2014-09-23:
> I'm assuming evolution-calendar-factory gets loaded by indicator-datetime initially such that the indicator can show calendar events.

As a troubleshooting step, I tried disabling the Upstart entry for
indicator-datetime-service so that it doesn't get started and respawned
automatically, and launched it manually using the terminal. Sure enough,
evolution-calendar-factory starts only after indicator-datetime-service
starts, and stops a few seconds after the indicator-datetime-service
process is terminated (by Ctrl-C during my testing).

So what actually happens in the workaround I posted earlier was that
invoking another instance of evolution-calendar-factory manually will
sever the link that the date/time indicator has to the calendar service.
The new, manually invoked evolution-calendar-factory instance that
replaced the old one will then terminate itself after a few seconds.

It should be fine for people like me who never use the calendar, but
people who do use the calendar should watch out.

There are a few questions I can think of at this point:
1. Is it by design that indicator-datetime-service needs continuous access to the org.gnome.evolution.dataserver.Calendar4 D-Bus service?
2. Does it really need to maintain a connection to that service even if the user doesn't use the calendar feature at all? (this needs to be asked because the current implementation of evolution-calendar-factory occupies an above-average amount of memory, even for empty calendars)
3. If not, what could be preventing it from disconnecting from the service once it's done with its business?

I'll try to see what else I can uncover.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1342123

Title:
  evolution-calendar-factory always running with high memory usage

Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

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