Network metrics provider registers as an observer with the network quality tracker (NQT). To access NQT, it needs to access content::NetworkService. However, calling content::GetNetworkService in Network metrics provider's constructor results in crash since the mojo bindings are not yet initialized.
To get around this, currently, Network metrics provider registers as an observer by calling it as part of PostAfterStartupTask(). However, that sometimes takes up to 10-20 seconds. We should figure out if there is a earlier place in the startup process where it is safe to call content::GetNetworkService() that happens before tasks posted via PostAfterStartupTask() are executed.
Comment 1 by tbansal@chromium.org
, Nov 21Status: WontFix (was: Assigned)