Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396017
Title:
Up
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396017
Title:
Upstart excessive cpu and memory consumption
To m
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396017
Titl
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
