mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-22 01:35:35 +00:00
3e70bf3ff1
Launching processes takes enough time that we should avoid blocking the parent process's IPC I/O thread for it; it's less bad for responsiveness than blocking the main thread, but it's not good. On Windows we need to use a dedicated thread, because the sandbox isn't thread-safe and it asserts that the same thread is used for every launch. Otherwise, a thread pool is used. (Or, in the Web Replay middleman process, where there isn't enough of XPCOM for any of this, launching the actual content processes remains on the I/O thread.) Depends on D15886 Differential Revision: https://phabricator.services.mozilla.com/D8946 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| app | ||
| chromium | ||
| contentproc | ||
| glue | ||
| ipdl | ||
| mscom | ||
| testshell | ||
| moz.build | ||
| pull-chromium.py | ||