touch-packages team mailing list archive

[Ted Gould <ted@xxxxxxxx>]

On Tue, 2015-08-04 at 20:43 +0000, Gerry Boland wrote:

> You're correct the OOM score set to 2 arbitrary values. They're
> hardcoded and set by upstart-app-launch. I believe your question is my
> question 2 above, to which I don't have an answer.


They're not entirely arbitrary, more or less built to try and have a
continuum of values. Basically trusted services (unity, etc.) are zero.
Then we put the focused application below that at 100. The dash is 200
so if there is no focused application it is the lowest. Then unfocused
applications are 900.

Hand-wavingly that means that a focused application would be allowed to
use 8 times as much memory as an unfocused application if memory size
was the only thing taken into account.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853

Title:
  OOM scoring kills the browser's render process while the browser is
  running

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  According to people's reports, the OOM killer kills the browser's
  renderer process while the browser is being focused.

  https://plus.google.com/u/1/106915287544632473346/posts/CoA8mLLvsJk?cfem=1

  Also the OOM scoring mechanism really should take more things into
  accounts. To me it happens frequently that an app is hanging unused in
  the right edge spread for days without getting killed, but the 2 most
  recent apps I switch between get killed all the time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478853/+subscriptions