1470201 - Move about: pages into its own content process

Status: RESOLVED WONTFIX

(Core :: DOM: Content Processes, enhancement)

Description

[Jay Lim [:imjching]]

Now that we have moved Activity Stream (about:newtab, about:home, and about:welcome) into its own about content process, we can also start moving other about: pages that currently run in content into their own special processes (possibly the same about content process?). This way, if normal content processes get compromised, they are separated via the process boundary from the powers and information inside the about: pages. Also, we can use the JS bytecode startup cache or the ScriptPreloader cache for possible browser startup win.

Comment 1

[Neha Kochar [:neha]]

Mike, is this already fixed by the privileged content process?

Comment 2

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

(In reply to Neha Kochar [:neha] from comment #1)

Mike, is this already fixed by the privileged content process?

No, not yet. The Privileged Content Process is currently (still) Nightly-only, and only about:newtab / about:home load in it for now. There's been some talk about loading about:config, about:preferences, and others in there, but we should make sure loading about:newtab / about:home works properly there before focusing on those other cases.

Comment 3

[Tim Spurway [:tspurway]]

Hey Mike,

Where does this bug belong?

Comment 4

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

Probably DOM :: Content Processes. Thanks. :)

Comment 5

[Chris Peterson [:cpeterson]]

Unblocking Fission because the about: pages that currently run in the parent process (such as about:config and about:preferences) don't need to move to a content process. kmag wonders whether we should just WONTFIX this bug.