Boot speed is significantly affected by installing apps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
click (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
lxc-android-config (Ubuntu) |
Fix Released
|
High
|
Jamie Strandboge |
Bug Description
Install a bunch of apps.
Reboot phone
Notice a significant lengthening of the boot process.
My nexus 4 takes 4 minutes to get to a Unity welcome screen.
If I adb shell in I can see a bunch of apparmor_parser processes running and a load average of 6.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: apparmor 2.8.0-0ubuntu28
ProcVersionSign
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.2-0ubuntu1
Architecture: armhf
Date: Thu Sep 19 11:48:59 2013
InstallationDate: Installed on 2013-09-18 (0 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130918.1)
MarkForUpload: True
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcKernelCmdline: console=
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Colin Watson: Approve
- Ubuntu CI managed package branches: Pending requested
-
Diff: 485 lines (+269/-70)11 files modifiedREADME (+1/-0)
click/build.py (+10/-22)
click/framework.py (+138/-0)
click/install.py (+8/-28)
click/paths.py.in (+1/-0)
click/tests/helpers.py (+29/-0)
click/tests/test_build.py (+39/-5)
click/tests/test_install.py (+2/-4)
debian/changelog (+8/-0)
doc/file-format.rst (+1/-2)
doc/index.rst (+32/-9)
Changed in apparmor (Ubuntu): | |
importance: | Critical → High |
This looks like a policy recompile happening on boot. Which means the policy cache is out of date.
Does this happen if you reboot. On a reboot the policy cache should be up to date, so that the apparmor_parser won't be compiling policy.