[Touch-packages] [Bug 1396017] Re: Upstart excessive cpu and memory consumption

2014-12-03 Thread Fabrizio F
Not true. Disabling the screen-lock, simply delays the problem but is unable to avoid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1396017 Title: Upstart excessive cpu

[Touch-packages] [Bug 1396017] Re: Upstart excessive cpu and memory consumption

2014-11-30 Thread Fabrizio F
Problem seems to disappear disabling the screen-lock functionality. if the displays can stay "on", upstart --user process is not a problem... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.laun

[Touch-packages] [Bug 1396017] Re: Upstart excessive cpu and memory consumption

2014-11-26 Thread Fabrizio F
I am experiencing the same problem. htop shows "upstart --user" till 36% MEM and 98% CPU, after 8-10 hours. No workaround found. .xession-erros is full of: "upstart: Temporary process spawn error: Cannot allocate memory" The only solution is to kill the process (or to restart lightdm...). -- Y