New issue
Advanced search Search tips

Issue 713806 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Mojo: content_plugin cannot access memory_instrumentation::mojom::Coordinator

Project Member Reported by marshall@chromium.org, Apr 20 2017

Issue description

Chrome Version: Master revision a106f0ab (#464641), M59 branch point
OS: Windows 10 64-bit

What steps will reproduce the problem?
(1) Run Chromium and load a PDF file.

What is the expected result?
No error messages in the console.

What happens instead?
Get the following error message:

[0420/140627.311:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser

Please use labels and text to provide additional information.
I believe this error is because "memory_instrumentation::mojom::Coordinator" is not listed under the "plugin" section of content/public/app/mojo/content_browser_manifest.json. It was likely introduced by http://crrev.com/6e4c507d.

PDF loading seems to work fine, so this is likely not a critical issue.

 
Owner: chiniforooshan@chromium.org
Status: Started (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/148ce9fd71f2aa0fa421b25821dbf36299d4e6c1

commit 148ce9fd71f2aa0fa421b25821dbf36299d4e6c1
Author: Ehsan Chiniforooshan <chiniforooshan@chromium.org>
Date: Mon Aug 14 15:40:01 2017

Expose mem. inst. coordinator in content browser

This groups interfaces that are OK to be used by any content browser
user under the "app" class. Also, it seems that "utility" class is
not used anywhere, in particular not in content_utility_manifest.json,
and so it is deleted.

BUG= 713806 

Change-Id: Icbe9f9741431269790d3a229542f6388d5276141
Reviewed-on: https://chromium-review.googlesource.com/612041
Commit-Queue: Ehsan Chiniforooshan <chiniforooshan@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#494054}
[modify] https://crrev.com/148ce9fd71f2aa0fa421b25821dbf36299d4e6c1/content/public/app/mojo/content_browser_manifest.json
[modify] https://crrev.com/148ce9fd71f2aa0fa421b25821dbf36299d4e6c1/content/public/app/mojo/content_gpu_manifest.json
[modify] https://crrev.com/148ce9fd71f2aa0fa421b25821dbf36299d4e6c1/content/public/app/mojo/content_plugin_manifest.json
[modify] https://crrev.com/148ce9fd71f2aa0fa421b25821dbf36299d4e6c1/content/public/app/mojo/content_renderer_manifest.json
[modify] https://crrev.com/148ce9fd71f2aa0fa421b25821dbf36299d4e6c1/content/public/app/mojo/content_utility_manifest.json

Status: Fixed (was: Started)
 Issue 771022  has been merged into this issue.

Sign in to add a comment