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

Issue 817033 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Service Manager -- cannot bind safe_browsing::mojom::PhishingDetectorClient

Project Member Reported by apaci...@chromium.org, Feb 27 2018

Issue description

Chrome Version: 66.0.3357.0
OS: linux

What steps will reproduce the problem?
(1) Build tip of tree (currently at commit 5381e7250d90e33ed29d7ce3df188c401bc4ad67)
(2) Enable dcheck
(3) Build and navigate to w3 media events site: https://www.w3.org/2010/05/video/mediaevents.html

What is the expected result?
No crash.

What happens instead?
NOTREACHED() hit here: https://cs.chromium.org/chromium/src/services/service_manager/service_manager.cc?l=154

The Service Manager prevented service "content_renderer" from binding interface "safe_browsing::mojom::PhishingDetectorClient" in target service "content_browser". You probably need to update one or more service manifests to ensure that "content_browser" exposes "safe_browsing::mojom::PhishingDetectorClient" through a capability and that "content_renderer" requires that capability from the "content_browser" service.

 

Comment 1 by vakh@chromium.org, Mar 16 2018

Labels: SafeBrowsing-Triaged
Owner: lpz@chromium.org

Comment 2 by lpz@chromium.org, Mar 16 2018

Mergedinto: 816892
Status: Duplicate (was: Assigned)

Sign in to add a comment