[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted

2017-03-13 Thread Michał Sawicz
** No longer affects: qtmir

-- 
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 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/ubuntu/+source/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


[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted

2014-10-31 Thread Ted Gould
** 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


[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted

2014-10-30 Thread Olli Ries
this bug needs to be targeted after RTM, via ota

** Tags removed: touch-2014-10-30
** Tags added: ota-1

-- 
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:
  In Progress
Status in “qtmir” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “qtmir” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

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


[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted

2014-10-27 Thread kevin gunn
** Tags removed: touch-2014-10-23
** Tags added: touch-2014-10-30

-- 
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:
  In Progress
Status in “qtmir” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “qtmir” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

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


[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted

2014-10-22 Thread Michał Sawicz
** Also affects: ubuntu
   Importance: Undecided
   Status: New

** Also affects: qtmir (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Package changed: ubuntu = qtmir (Ubuntu)

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity8 (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: qtmir (Ubuntu)
   Importance: Undecided = Critical

** Changed in: qtmir (Ubuntu)
   Status: New = In Progress

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) = Ted Gould (ted)

** Changed in: qtmir (Ubuntu RTM)
   Importance: Undecided = Critical

** Changed in: qtmir (Ubuntu RTM)
   Status: New = In Progress

** Changed in: qtmir (Ubuntu RTM)
 Assignee: (unassigned) = Ted Gould (ted)

** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity8 (Ubuntu)
   Status: New = In Progress

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Ted Gould (ted)

** Changed in: unity8 (Ubuntu RTM)
   Importance: Undecided = Critical

** Changed in: unity8 (Ubuntu RTM)
   Status: New = In Progress

** Changed in: unity8 (Ubuntu RTM)
 Assignee: (unassigned) = Ted Gould (ted)

-- 
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:
  In Progress
Status in “qtmir” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “qtmir” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

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