ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  Forks browser process to run sandbox IPC helper

Status in Oxide Webview:
  Fix Committed
Status in “oxide-qt” package in Ubuntu:
  New

Bug description:
  Chromium forks the browser process to run a sandbox IPC helper
  process, which provides a mechanism for sandboxed renderers to access
  things like the font cache. However, it does this without execing a
  new process image in the child.

  Whilst this is fine for Chromium  (because it forks at startup and
  before any threads are created), it is bad for us for a few reasons:

  By the time we "start" Chromium:
  - We already have a QML app and Qt gunk running in the browser process - I suspect that a lot of the memory used by the app will get copied eventually, which is a waste.
  - We already have many threads running. As threads don't get forked, the child process will deadlock if any thread held a lock it requires at some point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1304648/+subscriptions