Temporary workaround for high memory usage of evolution-calendar-
factory-subprocess
** Attachment added: "What to disable in online accounts"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1589605/+attachment/4678874/+files/Capture%20du%202016-06-07%2011-54-27.png
--
You
Hi @seb128 ,
I have tried disabling my three online Google accounts and the subprocess
disappears altogether. As soon as I re-enable one account with few Google
Agenda items, it comes back with ~ 50 Mio. When I enable the main account that
has a good many Google Agenda items, the subprocess
New bug filed under Bug #1589605 for the desktop install.
--
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:
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
@ogra Thanks, I wasn't at all aware that "Canonical System Image" was about
*mobile* systems. Maybe a more straightforward name would help… :)
I'll go look if this bug has already been filed under desktop installs.
--
You received this bug notification because you are a member of DX
Packages,
Plus, the nice little workaround does not seem to function in 16.04.
Simply re-invoking the process does not lead to it exiting. I've seen it
crash several times in a row with no obvious pattern to it (except it
happens fairly soon after login).
--
You received this bug notification because you
Still a major memory hog in 16.04 with a clean install (except for /home
obviously).
The process has changed names and is now dubbed
"evolution-calendar-factory-subprocess" but its behavior has not changed. After
a couple of minutes, memory usage is up to ~300 Mio, which is a bit steep for
@aj-sahagun
Works fine now. So apparently, when you want a couple of commands to be
launched one after the other in the startup list, you can't just write:
sleep 60;
You have to explicitly call bash -c like this:
bash -c 'sleep 60; '
Good to know!
--
You received this bug
@aj-sahagun
Thanks for your reply. I wasn't aware you had to explicitly call bash
when using the form "sleep 1m; ". I'll try it out.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions:
@aj-sahagun
I have the exact same problem. Adding an autostart entry did not help, for
reasons I do not understand. If I type it manually in a terminal, it works
fine. If I add an autostart entry with the exact same command, nothing happens
and evolution-calendar-factory happily nibbles away at
10 matches
Mail list logo
