1527929 - Make Preallocated Process Manager allocate earlier

Status: RESOLVED DUPLICATE of bug 1521839

(Core :: DOM: Content Processes, enhancement)

Description

[Mike Conley (:mconley) (:⚙️)]

The Preallocated Process Manager currently waits until an opportunity of idleness to preallocate the next content process.

We know when we start the browser we're going to need a content process. I think we should try to preallocate that first content process as soon as possible after the main process launches, so by the time that the initial remote frameloader is created, the content process it needs has long ago initialized itself and is ready to roll.

Comment 1

[Mike Conley (:mconley) (:⚙️)]

With bug 1527711, this would also mean that the initial privileged content process for about:home would also be preallocated, which would probably help improve our time to paint it.