SafeBrowsing creates its own URLRequestContext which "borrows" a lot of components of the main URLRequestContext, so not clear how to handle this. We need to figure out what to do about this when the network service is enabled. Policy requests also use this URLRequestContext.
We many need to punt this until have cookie store / channel ID store configuration working when the network service is enabled, though this issue does block updating consumers of Safebrowsing's cookie store.
Comment 1 by mmenke@chromium.org
, Nov 29 2017