unexpectedly large memory usage of mounted snaps
Bug #1636847 reported by
Zygmunt Krynicki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
Critical
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King | ||
Xenial |
Fix Released
|
Critical
|
Andy Whitcroft | ||
Yakkety |
Fix Released
|
Critical
|
Andy Whitcroft | ||
Zesty |
Fix Released
|
Medium
|
Colin Ian King |
Bug Description
This is a tracking bug for what might be kernel bugs or kernel configuration changes.
As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM.
The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps.
Changed in linux (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Yakkety): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
assignee: | nobody → Colin Ian King (colin-king) |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Yakkety): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Andy Whitcroft (apw) |
Changed in linux (Ubuntu Yakkety): | |
assignee: | nobody → Andy Whitcroft (apw) |
Changed in linux (Ubuntu Xenial): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Yakkety): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in snappy: | |
status: | New → In Progress |
importance: | Undecided → Critical |
Changed in snappy: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1636847
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.