touch-packages team mailing list archive

[Josh Arenson <1478853@xxxxxxxxxxxxxxxxxx>]

@greyback, it seems that upstart-app-launch just sets the score for
paused apps at 900, and changes them back to 100 after being resumed. I
wonder where these numbers came from, and how OOM Killer further
prioritizes processes with the same score. 900 seems pretty high, but I
really don't have much experience with this so I'm not sure. As a hack,
would reducing the score of Oxide (or whatever is actually affected by
this) by 30, or so, points have an impact?

-- 
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