1764662 - Starting the browser starts the socket process very early

Status: NEW

(Core :: Networking, defect, P3)

Description

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

This code in the DocumentChannel constructor will cause the socket process to be launched (and probably other initialization that could maybe be done later or async?) the first time it's used, and my understanding is that that happens fairly early, the first time we try to render any browser chrome. I don't know how significant this is, but it might have implications for perceived startup performance.

I noticed this in a case where Firefox would try to start, notice that the profile was locked, but fail to connect to the existing instance; in that case it just did a chrome alert about the error (and didn't ever display browser UI), and I had a system call tracer attached so I saw the socket process being started, which seemed unexpected in that situation.

Comment 1

[Kershaw Chang [:kershaw]]

Maybe we can wait to launch socket process until the first http load happens.