← Back to team overview

touch-packages team mailing list archive

[Bug 1478853] Re: OOM scoring kills the browser's render process while the browser is running

 

When in the background, the renderer process should be stopped together with its parent. However it will continue using memory.
The OOM killer should be instructed to kill stopped processes in priority, not sure how feasible that is though.

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

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