evolution-calendar-factory uses lots of memory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
evolution-data-server (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
indicator-datetime (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-
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-
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…
Thank you for your bug report, could you try to get a valgrind log showing the leak? is it linked to some specific calendar (can you repeat/try by disabling some accounts?)