New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 903948 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug
Proj-Servicification

Blocking:
issue 837753



Sign in to add a comment

Reporting (from the renderer) fails when NetworkService is enabled

Project Member Reported by eroman@chromium.org, Nov 9

Issue description

When the renderer generates a deprecation or intervention report, it uses mojom::ReportingServiceProxy to queue it to the reporting service.

The receiving end looks to be running in the browser process as content::ReportingServiceProxyImpl (content/browser/net/), and tries to forward it to the reporting service hanging off the URLRequestContext. Which will presumably be missing when NetworkService is enabled:

https://chromium.googlesource.com/chromium/src/+/HEAD/content/browser/net/reporting_service_proxy.cc#132
 
Labels: -Pri-3 Proj-Servicification-Stable OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows Pri-2
Thanks. Looks like we have NetworkContext::QueueReport recently, so we can use that interface always instead of reaching into net/ (it would work in both network service enabled and disabled).

Eric: do you have time to do this or should we find another owner?
Owner: eroman@chromium.org
Status: Assigned (was: Untriaged)
Sure I can take this!

As you pointed out, it shouldn't be a big change.
Thanks
Blocking: 837753
Cc: ddcreager@chromium.org
Cc: -ddcreager@chromium.org dcreager@chromium.org
Labels: Hotlist-KnownIssue
Project Member

Comment 8 by bugdroid1@chromium.org, Nov 29

Status: Fixed (was: Assigned)

Sign in to add a comment