ubuntu-webapps-bugs team mailing list archive

[Jean-Baptiste Lallement <jean-baptiste.lallement@xxxxxxxxxx>]

Actually the tuning of the memory consumption of oxide/chromium fixed
the problem.

** Changed in: canonical-devices-system-image
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
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:
  Won't Fix
Status in Oxide:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
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