** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579799
Title:
Need API to allow shell to choose custom OOM k
Thanks for this Ted!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579799
Title:
Need API to allow shell to choose custom OOM killer scores
To manage notifications about this bug go to:
https://bu
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => Fix Committed
** Changed in: canonical-devices-system-image
Importance: Undecided => Wishlist
** Changed in: canonical-devices-system
This bug was fixed in the package ubuntu-app-launch -
0.9+16.10.20160825-0ubuntu1
---
ubuntu-app-launch (0.9+16.10.20160825-0ubuntu1) yakkety; urgency=medium
* Use at() instead of operator[]() so that we get an exception on
bounds checking
-- Ted Gould Thu, 25 Aug 2016 14:43
** Changed in: ubuntu-app-launch (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579799
Title:
Need API to allow shell to choose custom OOM killer sco
** Branch linked: lp:~ted/ubuntu-app-launch/lp1579799-oom-adjust
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579799
Title:
Need API to allow shell to choose custom OOM killer scores
To manage no
** Changed in: ubuntu-app-launch (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579799
Title:
Need API to allow shell to choose custom OOM killer scor
Spent a bit of time going back and forth on this with tvoss. We don't
want to have a ton of application states, that'll make insanity, but it
does make sense for qtmir to drive policy for applications. We don't
know completely what that policy is today.
Long story short, the plan is to provide an
Today UAL has basically three states for applications, on, off and
paused. There are then OOM scores associated with those states. And it
seems that this is requesting more states. But I'm not sure I
understand. For instance, for X11 apps they're never paused, so their
OOM score stays the same as t
