Currently the process launching thread is in browser_main_loop. Since it is only used for launching a new process, it should be owned by child process launcher, and is lazy initialized upon a request to launch process.
Np, one more coming down the pipe :) https://chromium-review.googlesource.com/c/chromium/src/+/963361. PROCESS_LAUMCHER was the very last string of a very long cleanup of BrowserThreads, glad we can finally remove all of these temporary APIs and guards :).
Having only UI/IO remaining will allow even further cleanup in issue 821034 :).
PS: did you see my comment on your original CL? You should use LazySingleThreadTaskRunner instead of a NoDestructor<SingleThreadTaskRunner> because the former will guarantee recycling in unit tests that go through multiple ScopedTaskEnvironment on the same process.
Comment 1 by hanxi@chromium.org
, Feb 23 2018