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

Issue 672965 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 661417
Owner:
please use my google.com address
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

logcat says during Telemetry test "Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService"

Project Member Reported by charliea@chromium.org, Dec 9 2016

Issue description

Test logs: https://storage.cloud.google.com/chromium-android/logcat_dumps/Android%20Nexus9%20Perf%20(3)/3730

Error message: 

03484:  12-08 03:37:41.870   768   768 E chromium: [ERROR:interface_registry.cc(210)] Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService requested by: content_renderer exposed by: content_browser via InterfaceProviderSpec "navigation:frame".

I wasn't able to figure out exactly which benchmark this was happening for, although I might be able to find it out with some work if you need it.
 
Cc: -charliea@google.com
/bump

Any idea when you might be able to take a look at this Ken?

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

I'm looking today
Sounds great. Thanks!

Comment 5 by roc...@chromium.org, Dec 12 2016

I suspect this must mean that the code which registers the DistillabilityService request handler:

https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/dom_distiller/ReaderModeManager.java?rcl=0&l=582

->

https://cs.chromium.org/chromium/src/components/dom_distiller/content/browser/android/java/src/org/chromium/components/dom_distiller/content/DistillablePageUtils.java?rcl=0&l=49

->

https://cs.chromium.org/chromium/src/components/dom_distiller/content/browser/distillable_page_utils_android.cc?rcl=0&l=70

-> 

https://cs.chromium.org/chromium/src/components/dom_distiller/content/browser/distillable_page_utils.cc?rcl=0&l=105

hasn't run by the time an incoming interface request arrives.

Not sure if this is a race with legacy IPC, or we're failing to observe some other event.

In general it does seem unfortunate that we have to wait for something to happen in Java code before registering an interface request handler. Can we avoid that?
Any luck in figuring out how to resolve this?
Cc: sa...@chromium.org
Not yet. I believe I meant to add sammc@ with my last comment for some insight into Java interface registration.

Comment 8 by sa...@chromium.org, Jan 4 2017

Mergedinto: 661417
Status: Duplicate (was: Assigned)

Sign in to add a comment