New issue
Advanced search Search tips

Issue 898304 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 21
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Determine a way to determine when it's safe to access Network Service

Project Member Reported by tbansal@chromium.org, Oct 23

Issue description

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.
 
Components: Internals>Network>NetworkQuality
Status: WontFix (was: Assigned)
Does not seem super critical.

Sign in to add a comment