If anyone is interested in a workaround, here's something that seems to
work on my Ubuntu install.
I noticed that running /usr/lib/evolution/evolution-calendar-factory by
itself manually will cause it to perform some initializations and
terminate after a few seconds. I'm not using any calendar-related
services.
--------
Registering ECalBackendContactsEventsFactory ('contacts:VEVENT')
<<snip>>
Registering ECalBackendCalDAVTodosFactory ('caldav:VTODO')
Server is up and running...
Bus name 'org.gnome.evolution.dataserver.Calendar4' acquired.
Bye.
--------
I also noticed that if I ran /usr/lib/evolution/evolution-calendar-
factory while there is already an instance running, the new instance
will take over the 'org.gnome.evolution.dataserver.Calendar4' bus and
will cause the older one to terminate:
--------
Registering ECalBackendContactsEventsFactory ('contacts:VEVENT')
<<snip>>
Registering ECalBackendCalDAVTodosFactory ('caldav:VTODO')
Server is up and running...
Bus name 'org.gnome.evolution.dataserver.Calendar4' acquired.
<<launch another instance in another terminal>>
Bus name 'org.gnome.evolution.dataserver.Calendar4' lost.
Bye.
--------
Since I'm not using any calendar-related services, I added a startup
item via GUI that invokes /usr/lib/evolution/evolution-calendar-factory
without any options:
--------
> cat ~/.config/autostart/evolution-calendar-factory.desktop
[Desktop Entry]
Type=Application
Exec=/usr/lib/evolution/evolution-calendar-factory
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name=Workaround for evolution-calendar-factory
--------
This causes the original "stuck" startup process to lose its hold on
org.gnome.evolution.dataserver.Calendar4 and terminate.
This workaround is a lot less invasive than the suggestions I have seen
elsewhere to uninstall packages or remove the file's execute bit, since
org.gnome.evolution.dataserver.Calendar4 will still be available.
Again, this is a workaround. Unfortunately, I haven't been able to find
out what causes the process to be stuck in the first place, or whether
or not it really needs to run all the time.
--
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:
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
--
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
