Runaway init --user consuming CPU and RAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
My Unity 8 froze on my Nexus 4. After connecting it to USB and adb shell, I found that 'init --user' was using 100% CPU and 60% RAM (> 1g). I ran "ubuntu-bug upstart" while it was still running to try and gather any information about what it was doing.
root@ubuntu-
current build number: 32
device name: mako
channel: trusty
last update: 2013-11-27 13:22:03
version version: 32
version ubuntu: 20131126.2
version device: 20131126
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: upstart 1.11-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.7-0ubuntu1
Architecture: armhf
Date: Wed Dec 4 14:08:43 2013
InstallationDate: Installed on 2013-11-26 (8 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131126.2)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SHELL=/bin/bash
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: Session
UpstartRunningS
UpstartRunningS
upstart.
upstart.
upstart.
upstart.
upstart.
upstart.
Changed in upstart (Ubuntu): | |
status: | New → Incomplete |
Changed in upstart (Ubuntu): | |
status: | Incomplete → New |
Hi Michael - thanks for raising this bug. However, none of the expected files that apport should have collected are attached. Added to which, I don't have a Nexus 4.
Do you have a crash file or any further details on what might have triggered this? Had the device been running for a long time? Had it just been updated via apt, etc.
Is this problem recreateable? If so, please grab an strace of the Session Init (re-nicing if required) and then maybe kill -ABRT to force a crash that apport will deal with.
The only detail I can glean from this bug which might be relevant is "UpstartRunning SessionCount: 2". I would have expected a count of 1.