touch-packages team mailing list archive

[David Barth <david.barth@xxxxxxxxxxxxx>]

At this stage we have a series of optimizations to deal with that
situation :

- a crash handler for webapps, which prevents the appearance of blank webviews - https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1375215
- a memory limit adjustment in Oxide - https://bugs.launchpad.net/oxide/+bug/1498953
- another opportunity to limit memory usage with the Skia font cache - https://bugs.launchpad.net/oxide/+bug/1499479

But at the root of that we would need to receive a signal in low memory situations, ie :
- adding the API to the app. lifecycle
- implementing the mechanisms to detect and notify apps of the low memory condition

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