** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@Ivan, we are going to fix snapd for the excessive memory usage.
AppArmor upstream already uses expr-simplify by default and newer
release of Ubuntu use parser.conf to set -O no-expr-simplify so users
can manage the setting like any other conffile.
--
You received this bug notification because
The biggest problem is that it isn't easily disabled because it is hardcoded in
the script instead of being in /etc/apparmor/parser.conf.
Instead of hardcoding, it would had been better to just update that conffile
and let dpkg update it if the user didn't change it (which is highly likely) or
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
@Sergio: your issue is different. It is being killed during a kernel
operation (sys_write) due to a vmalloc failure, where this bug is
occurring during a userspace compile. Please open a new bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Hi, running the snapd tests on i386 I see the following error that could
be related to this. It is failing with pc-kernel on beta and candidate
but I coun't reproduce it with the version on stable.
> snap list
Name VersionRev Tracking Publisher Notes
core 16-2.39.1
** Summary changed:
- apparmor fails to start with no parser errors
+ apparmor uses excessive memory leading to oom kill
** Description changed:
+ When attempting to load the profile from comment #7, apparmor uses
+ excessive amounts of memory leading to being killed by the OOM killer
+ and
7 matches
Mail list logo
