OOM killer score calculations should be improved
Bug #1583209 reported by
Michael Zanetti
This bug report is a duplicate of:
Bug #1579799: Need API to allow shell to choose custom OOM killer scores.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
New
|
High
|
kevin gunn | ||
qtmir (Ubuntu) |
Confirmed
|
High
|
Nick Dedekind | ||
ubuntu-app-launch (Ubuntu) |
Confirmed
|
High
|
Ted Gould |
Bug Description
There are a couple of issues with the current way of calculating the OOM score. It happens that the two frequently used apps are killed repeatedly, while there are many other apps sitting in the right edge not being killed. This also manifests in issues like bug 1421241.
I think the OOM score calculation should take recency of use into account instead of only looking at memory usage of an app. The memory usage might still be taken into account as it could indeed make sense to kill one large app instead of 5 small ones, but not if that one large app is the one that the user keeps on switching to.
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
assignee: | nobody → kevin gunn (kgunn72) |
Changed in qtmir (Ubuntu): | |
importance: | Undecided → High |
Changed in ubuntu-app-launch (Ubuntu): | |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
milestone: | none → backlog |
Changed in ubuntu-app-launch (Ubuntu): | |
assignee: | nobody → Ted Gould (ted) |
Changed in qtmir (Ubuntu): | |
assignee: | nobody → Gerry Boland (gerboland) |
Changed in qtmir (Ubuntu): | |
assignee: | Gerry Boland (gerboland) → Nick Dedekind (nick-dedekind) |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.