Public bug reported:
As filed under bug #1342123 (under Canonical System Image, i.e. for mobile
installs) by several users, including desktop installs,
evolution-calendar-factory (previsouly in 14.04) then
evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of
megabytes of memory (~ 300 Mio in my case).
This might have to do with having lots of linked calendars (Google Agenda or
other). Another user on my system has much fewer Google Agendas than me and her
memory usage of evolution-calendar-factory-subprocess is less, but still close
to 100 Mio.
There have been random crashes of the process, mostly directly upon login,
always caused by addressing memory out of range.
There used to be a workaround by invoking the process a second time, which
caused it to exit more or less gracefully. This is not the case anymore in
16.04.
Unfortunately, searching Google leads to the bug #1342123 which concerns
"Canonical System Image", and several users have replied even though it does
not only concern mobile installs, which is not immediately self-evident when
you are not aware what "Canonical System Image" stands for…
** Affects: evolution (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: evolution-data-server (Ubuntu)
Importance: High
Status: Incomplete
** Affects: indicator-datetime (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: evolution memory
** Description changed:
As filed under bug #1342123 (under Canonical System Image, i.e. for mobile
installs) by several users, including desktop installs,
evolution-calendar-factory (previsouly in 14.04) then
evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of
megabytes of memory (~ 300 Mio in my case).
- This might have to do with having lots of linked calendars (Google Agenda or
other). Another user on my system has much fewer Google Agendas than me and her
memory usage of evolution-calendar-factory-subprocess is far les (but still
close to 100 Mio).
+ This might have to do with having lots of linked calendars (Google Agenda or
other). Another user on my system has much fewer Google Agendas than me and her
memory usage of evolution-calendar-factory-subprocess is less, but still close
to 100 Mio.
There have been random crashes of the process, mostly directly upon login,
always caused by addressing memory out of range.
There used to be a workaround by invoking the process a second time, which
caused it to exit more or less gracefully. This is not the case anymore in
16.04.
Unfortunately, searching Google leads to the bug #1342123 which concerns
"Canonical System Image", and several users have replied even though it does
not only concern mobile installs, which is not immediately self-evident when
you are not aware what "Canonical System Image" stands for…
** Also affects: evolution (Ubuntu)
Importance: Undecided
Status: New
** Also affects: evolution-data-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589605
Title:
evolution-calendar-factory uses lots of memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
