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

Issue 675051 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 662040
Owner:
please use my google.com address
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[ERROR:interface_registry.cc(210)] Failed to locate a binder for interface

Reported by kmans...@gmail.com, Dec 16 2016

Issue description

Steps to reproduce the problem:
I'm an Android developer whose app uses WebView.

There is a new logcat "error" message since 56.0.2924.23 or so.

Bo Lio here: https://bugs.chromium.org/p/chromium/issues/detail?id=647291#c35 thought that it should be appear in the logcat.

chromium  E  [ERROR:interface_registry.cc(210)] Failed to locate a binder for interface: autofill::mojom:
   :PasswordManagerDriver requested by: content_renderer exposed by: content_browser via Interf
   aceProviderSpec "navigation:frame".
E  InterfaceRegistry(navigation:frame):
E  Owned by:
E    content_browser@ run as: e12dde29-690a-49b0-a804-f9a61b44bce6
E    Providing:
E      capability: renderer containing interfaces:
E        autofill::mojom::AutofillDriver
E        autofill::mojom::PasswordManagerDriver
E        blink::mojom::MediaSessionService
E        blink::mojom::PermissionService
E        blink::mojom::PresentationService
E        blink::mojom::SensitiveInputVisibilityService
E        blink::mojom::ShapeDetection
E        blink::mojom::WebBluetoothService
E        blink::mojom::WebSocket
E        content::mojom::BrowserTarget
E        device::VibrationManager
E        device::mojom::GeolocationService
E        device::mojom::SensorProvider
E        device::mojom::VRService
E        device::mojom::WakeLockService
E        device::nfc::mojom::NFC
E        device::usb::DeviceManager
E        media::mojom::InterfaceFactory
E        media::mojom::RemoterFactory
E        media::mojom::Renderer
E        mojom::MediaDevicesDispatcherHost
E        payments::mojom::PaymentRequest
E        web_restrictions::mojom::WebRestrictions
E    Requiring:
E      From: content_renderer:
E        browser
E  Bound to:
E    content_renderer@2_1 run as: e12dde29-690a-49b0-a804-f9a61b44bce6
E    Providing:
E      capability: browser containing interfaces:
E        autofill::mojom::AutofillAgent
E        autofill::mojom::PasswordAutofillAgent
E        autofill::mojom::PasswordGenerationAgent
E        blink::mojom::AppBannerController
E        content::mojom::ImageDownloader
E        mojom::MediaDevicesListener
E    Requiring:
E      From: content_browser:
E        renderer
E  Binders registered for:
E   * autofill::mojom::AutofillDriver
E   * blink::mojom::MediaSessionService
E   * blink::mojom::PermissionService
E   * blink::mojom::PresentationService
E   * blink::mojom::ShapeDetection
E   * blink::mojom::WebBluetoothService
E   * blink::mojom::WebSocket
E   * device::VibrationManager
E   * device::mojom::GeolocationService
E   * device::mojom::VRService
E   * device::mojom::WakeLockService
E   * device::nfc::mojom::NFC
E   * media::mojom::InterfaceFactory
E   * mojom::MediaDevicesDispatcherHost
E   * web_restrictions::mojom::WebRestrictions
E   * - denotes an interface exposed to remote per policy.

What is the expected behavior?

What went wrong?
Spruous (to me, an outsider) error message in logcat.

Did this work before? N/A 

Chrome version: 56.0.2924.23  Channel: beta
OS Version: 6.0
Flash Version: N/A

Noticed in version 56.0.2924.23. Wasn't there 2-3 weeks ago, I don't think.
 

Comment 1 by boliu@chromium.org, Dec 16 2016

Components: Internals>Mojo Mobile>WebView
Status: Available (was: Unconfirmed)
we should not spam the log, despite  http://crbug.com/662040#c50 

Comment 2 by ti...@chromium.org, Dec 16 2016

Cc: m...@chromium.org boliu@chromium.org
Owner: roc...@chromium.org
Status: Assigned (was: Available)
Original CL that added the dump is https://codereview.chromium.org/2457493004.
It was modified to put in VLOG(1) instead of LOG(ERROR) in https://codereview.chromium.org/2504803002, but then reverted in https://codereview.chromium.org/2498203004.

Why the VLOG(1) portion was reverted?

Comment 3 by roc...@chromium.org, Dec 16 2016

Mergedinto: 662040
Status: Duplicate (was: Assigned)
Because it's an indication of an actual error in chromium and shouldn't be disregarded as log spam.

Sign in to add a comment