Forks browser process to run sandbox IPC helper
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Fix Released
|
Critical
|
Unassigned | ||
oxide-qt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
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.
Changed in oxide: | |
importance: | Undecided → Critical |
status: | New → Triaged |
status: | Triaged → Fix Committed |
Changed in oxide: | |
status: | Fix Committed → Fix Released |
Awesome! Thank (again) you for the fix Chris :)