Currently, when the network service is enabled, we still create a stub in-process URLRequestContext, which causes a lot of tests of code that's not network-service-ready to incorrectly pass, since it can be used to make URLRequests, DNS requests, access the network quality estimator, etc.
We should look into disabling it in tests, so we have a better way of discovering code that depends on the legacy in-process network stack. Unfortunately, if we just removed the in-process URLRequestContext completely, all browser tests would crash. There are enough things going on at startup that have hard dependencies on the legacy pathway that even just disabling it for tests will be a major undertaking.
Comment 1 by jam@chromium.org
, Mar 23 2018Status: Assigned (was: Untriaged)
Summary: Don't use URLRequestContexts in the browser when network service is enabled (was: Add a way to disable the legacy in-process URLRequestContext)