** Changed in: qtmir
Status: In Progress => Fix Released
** Changed in: qtmir (Ubuntu)
Status: In Progress => Fix Released
** Changed in: qtmir (Ubuntu RTM)
Status: In Progress => Fix Released
** Changed in: unity8 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: unity8 (Ubuntu RTM)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1379788
Title:
Oxide processes don't get OOM adjusted
Status in Qt integration with the Mir display server:
Fix Released
Status in “qtmir” package in Ubuntu:
Fix Released
Status in “unity8” package in Ubuntu:
Fix Released
Status in “qtmir” package in Ubuntu RTM:
Fix Released
Status in “unity8” package in Ubuntu RTM:
Fix Released
Bug description:
OOM adjustment is important to the lifecycle because it makes it so
that the focused application actually gets the full usage of the
device. By not OOM adjusting the Oxide renders, some of the largest
processes in the system aren't killed appropriately by the OOM killer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1379788/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
