We have the `PreallocatedProcessManager` (which is currently [disabled on Android](https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/mobile/android/app/geckoview-prefs.js#191-192)) to kick this initialization off before we get to `ContentParent::CreateBrowser`. But it seems like `PreallocatedProcessManager` doesn't actually have an API to start a preallocation before we ask for the first process. Once we fix this bug and the Gecko stuff in the content process starts running earlier, it should also avoid the synchronous wait on the parent process that I filed as bug 1958065.
Bug 1924849 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We have the `PreallocatedProcessManager` (which is currently [disabled on Android](https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/mobile/android/app/geckoview-prefs.js#191-192), bug 1937836) to kick this initialization off before we get to `ContentParent::CreateBrowser`. But it seems like `PreallocatedProcessManager` doesn't actually have an API to start a preallocation before we ask for the first process. Once we fix this bug and the Gecko stuff in the content process starts running earlier, it should also avoid the synchronous wait on the parent process that I filed as bug 1958065.
We have the `PreallocatedProcessManager` (which is currently [disabled on Android](https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/mobile/android/app/geckoview-prefs.js#191-192), bug 1937836) to kick this initialization off before we get to `ContentParent::CreateBrowser`. But it seems like `PreallocatedProcessManager` doesn't actually have an API to start a preallocation before we ask for the first process. It also currently only kicks of preallocation during idle, and we're never idle during startup. Once we fix this bug and the Gecko stuff in the content process starts running earlier, it should also avoid the synchronous wait on the parent process that I filed as bug 1958065. We may want to consider preallocating two processes rather than just one, i.e. one for the content process and one for the WebExtensions process, to fix bug 1958327 at the same time.
We have the `PreallocatedProcessManager` (which is currently [disabled on Android](https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/mobile/android/app/geckoview-prefs.js#191-192), bug 1937836) to kick this initialization off before we get to `ContentParent::CreateBrowser`. But it seems like `PreallocatedProcessManager` doesn't actually have an API to start a preallocation before we ask for the first process. It also currently only kicks of preallocation during idle, and we're never idle during startup. Once we fix this bug and the Gecko stuff in the content process starts running earlier, it should also avoid the synchronous wait on the parent process that I filed as bug 1958065. And we should probably preallocate two processes rather than just one, one for the content process and one for the WebExtensions process, to fix bug 1958327 at the same time.