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

Issue 661009 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Visiting chrome://site-engagement crashes the renderer

Project Member Reported by dominickn@chromium.org, Nov 1 2016

Issue description

Version: 56.0.2905.0 (Canary).
OS: Mac OS X 10.11

What steps will reproduce the problem?
(1) Launch chrome
(2) Visit chrome://site-engagement

What is the expected output?

Renderer does not crash (it did not crash in 56.0.2902.0)

What do you see instead?

Renderer crashes. Running Chrome from the command line gives the following output in the terminal:

[64212:1295:1101/112959:ERROR:interface_registry.cc(160)] InterfaceProviderSpec "navigation:frame" prevented service: service:content_renderer from binding interface: media_router::mojom::MediaRouter exposed by: service:content_browser
[64212:1295:1101/112959:ERROR:render_process_host_impl.cc(2980)] Terminating render process for bad Mojo message: Received bad user message: InterfaceProviderSpec "navigation:frame" prevented service: service:content_renderer from binding interface: media_router::mojom::MediaRouter exposed by: service:content_browser
[64212:1295:1101/112959:ERROR:bad_message.cc(23)] Terminating renderer for bad IPC message, reason 123

Is this due to a recent mojo change or is it a bug in the media router mojo implementation?
 
Should be fixed by https://codereview.chromium.org/2468503003
Cc: -mfo...@chromium.org
Mergedinto: 660772
Owner: ----
Status: Duplicate (was: Assigned)

Sign in to add a comment