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

Issue 660903 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
please use my google.com address
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

start task manager gets some mojo console output

Project Member Reported by xidac...@chromium.org, Oct 31 2016

Issue description

Here is the output:

InterfaceRegistry(service_manager:connector):
Owned by:
  service:content_gpu@4 run as: 505C0EE9-3013-43C0-82B0-A84F50CF8D84

  Providing:
    capability: browser containing interfaces:
      IPC::mojom::ChannelBootstrap
      arc::mojom::VideoAcceleratorService
      arc::mojom::VideoAcceleratorServiceClient
      service_manager::mojom::ServiceFactory
    capability: service_manager:service_factory containing interfaces:
      service_manager::mojom::ServiceFactory

  Requiring:
    From: service:content_browser:
      gpu

Bound to:
  service:content_browser@ run as: 505C0EE9-3013-43C0-82B0-A84F50CF8D84

  Providing:
    capability: ash containing interfaces:
      ash::mojom::LocaleNotificationController
      ash::mojom::NewWindowClient
      ash::mojom::ShelfController
      ash::mojom::SystemTray
      ash::mojom::SystemTrayClient
      ash::mojom::VolumeController
      ash::mojom::WallpaperController
      ash::mojom::WallpaperManager
      keyboard::mojom::Keyboard
    capability: gpu containing interfaces:
      device::mojom::PowerMonitor
      metrics::mojom::CallStackProfileCollector
    capability: mash:launchable containing interfaces:
      mash::mojom::Launchable
    capability: plugin containing interfaces:
      device::mojom::PowerMonitor
    capability: renderer containing interfaces:
      autofill::mojom::AutofillDriver
      autofill::mojom::PasswordManagerDriver
      blink::mojom::BackgroundSyncService
      blink::mojom::BroadcastChannelProvider
      blink::mojom::BudgetService
      blink::mojom::Hyphenation
      blink::mojom::MimeRegistry
      blink::mojom::NotificationService
      blink::mojom::OffscreenCanvasCompositorFrameSinkProvider
      blink::mojom::OffscreenCanvasSurface
      blink::mojom::PermissionService
      blink::mojom::ShapeDetection
      blink::mojom::WebSocket
      content::mojom::MemoryCoordinatorHandle
      content::mojom::ServiceWorkerDispatcherHost
      content::mojom::StoragePartitionService
      content::mojom::URLLoaderFactory
      content::mojom::VideoCaptureHost
      device::BatteryMonitor
      device::mojom::LightSensor
      device::mojom::MotionSensor
      device::mojom::OrientationSensor
      device::mojom::PowerMonitor
      device::mojom::TimeZoneMonitor
      extensions::StashService
      media::mojom::ImageCapture
      memory_coordinator::mojom::MemoryCoordinatorHandle
      metrics::mojom::LeakDetector
      rappor::mojom::RapporRecorder
      startup_metric_utils::mojom::StartupMetricHost
      translate::mojom::ContentTranslateDriver
    capability: service_manager:service_factory containing interfaces:
      service_manager::mojom::ServiceFactory

  Requiring:
    From: *:
      app
    From: service:ash:
      ash
    From: service:content_browser:
      ash
    From: service:content_gpu:
      browser
    From: service:content_plugin:
      browser
    From: service:content_renderer:
      browser
    From: service:content_utility:
      browser
    From: service:file:
      file:filesystem
      file:leveldb
    From: service:media:
      media:media
    From: service:service_manager:
      service_manager:client_process
      service_manager:instance_name
      service_manager:user_id

Binders registered for:
 * IPC::mojom::ChannelBootstrap

 * - denotes an interface exposed to remote per policy.
 
Will do bisect.
Cc: roc...@chromium.org
Labels: OS-Linux
Owner: ben@chromium.org
Status: Assigned (was: Untriaged)
Bisect points to here:

https://chromium.googlesource.com/chromium/src/+log/0aa1406119dc85097efebbb282895b543e4b0c26..cfe99fb237d62af9535ee41c4469062299523fc9

Most likely:
https://codereview.chromium.org/2457493004

PTAL

Comment 3 by roc...@chromium.org, Oct 31 2016

What does "start task manager" mean?
Oh, sorry for any confusion. Basically starts chromium from a terminal, then press shift+esc to open the task manager, then observe the console output.

Comment 5 by roc...@chromium.org, Oct 31 2016

Ah. The more interesting log message precedes the bits pasted above:

[9600:9632:1031/112834:ERROR:interface_registry.cc(216)] InterfaceProviderSpec "service_manager:connector" prevented service: service:content_browser from binding interface: mojom::ResourceUsageReporter exposed by: service:content_gpu

Looks like the utility manifest overlay isn't adding this capability for browser.

Comment 6 by roc...@chromium.org, Oct 31 2016

Cc: -roc...@chromium.org ben@chromium.org
Owner: roc...@chromium.org
Status: Started (was: Assigned)
Project Member

Comment 7 by bugdroid1@chromium.org, Oct 31 2016

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

commit 67c1db0e0886747ccb550b0df67394cfa5d5f312
Author: rockot <rockot@chromium.org>
Date: Mon Oct 31 20:54:37 2016

Fix mojom::ResourceUsageReporter exposure via content child capabilities

Adds the interface to the browser capability for content_gpu in
Chrome's overlay.

Moves the interface from content_renderer_manifest.json to Chrome's
content_renderer overlay where it belongs.

Adds a Chrome overlay for content_plugin and adds the interface
there as well.

BUG= 660903 
R=ben@chromium.org,tsepez@chromium.org

Review-Url: https://codereview.chromium.org/2464693004
Cr-Commit-Position: refs/heads/master@{#428804}

[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/app/BUILD.gn
[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/app/mash/mash_service_overrides.json
[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/browser/browser_resources.grd
[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/browser/chrome_content_browser_client.cc
[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/browser/chrome_content_gpu_manifest_overlay.json
[add] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/browser/chrome_content_plugin_manifest_overlay.json
[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/chrome/browser/chrome_content_renderer_manifest_overlay.json
[modify] https://crrev.com/67c1db0e0886747ccb550b0df67394cfa5d5f312/content/public/app/mojo/content_renderer_manifest.json

Comment 8 by roc...@chromium.org, Oct 31 2016

Status: Fixed (was: Started)
Note: There is still some console output due to the fact that the GPU process does not register a ResourceUsageReporter handler. I consider this a separate issue though.
Status: Assigned (was: Fixed)
Re-open this. Opening context_shell gets this message right away. Please have a look.
Status: Fixed (was: Assigned)
Please do not reopen this bug, but file a new one, as it is almost certainly not the same bug.

The log message should contain more information than just this spec dump, and that information disambiguates one bug from another, specifically mentioning an interface which is not properly registered in the spec.
Please see comment #5 for what the more useful log message should look like.
Cc: xidac...@chromium.org
^

Sign in to add a comment