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

Issue 664989 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

--deterministic and --screenshot broken for headless_shell

Project Member Reported by alexclarke@chromium.org, Nov 14 2016

Issue description

cr run headless_shell -window-size=800x600 --no-sandbox --deterministic-fetch --screenshot  http://example.com
Contains a screenshot containing the stylesheet.

I notice a possible mojo problem:

[1114/141929:ERROR:interface_registry.cc(210)] Failed to locate a binder for interface: media::mojom::RemoterFactory requested by: service:content_renderer exposed by: service:content_browser via InterfaceProviderSpec "navigation:frame".

InterfaceRegistry(navigation:frame):
Owned by:
  service:content_browser@ run as: 66a28f83-53b3-4193-b8ed-cefab19c4a67

  Providing:
    capability: renderer containing interfaces:
      autofill::mojom::AutofillDriver
      autofill::mojom::PasswordManagerDriver
      blink::mojom::MediaSessionService
      blink::mojom::PermissionService
      blink::mojom::PresentationService
      blink::mojom::SensitiveInputVisibilityService
      blink::mojom::ShapeDetection
      blink::mojom::WebBluetoothService
      blink::mojom::WebSocket
      content::mojom::BrowserTarget
      device::VibrationManager
      device::mojom::GeolocationService
      device::mojom::SensorProvider
      device::mojom::VRService
      device::mojom::WakeLockService
      device::nfc::mojom::NFC
      device::usb::DeviceManager
      embedder_test::TestEmbedderService
      media::mojom::InterfaceFactory
      media::mojom::RemoterFactory
      media::mojom::Renderer
      mojom::MediaDevicesDispatcherHost
      payments::mojom::PaymentRequest

  Requiring:
    From: service:content_renderer:
      browser

Bound to:
  service:content_renderer@3_1 run as: 66a28f83-53b3-4193-b8ed-cefab19c4a67

  Providing:
    capability: browser containing interfaces:
      blink::mojom::AppBannerController
      content::mojom::ImageDownloader
      mojom::MediaDevicesListener

  Requiring:
    From: service:content_browser:
      renderer

Binders registered for:
 * blink::mojom::MediaSessionService
 * blink::mojom::PermissionService
 * blink::mojom::PresentationService
 * blink::mojom::WebBluetoothService
 * blink::mojom::WebSocket
 * device::VibrationManager
 * device::mojom::GeolocationService
 * device::mojom::WakeLockService
 * media::mojom::InterfaceFactory
 * mojom::MediaDevicesDispatcherHost

 * - denotes an interface exposed to remote per policy.

 
See  https://crbug.com/664154  for the mojo bug. Don't think it affects this screenshot problem. (The missing service isn't used in our case, otherwise we'd fail irrecoverably.)

Sounds like the source is displayed instead of the rendered page. Maybe some sort of content-type issue?
I think there's a bug with the handling of the headers with --deterministic I notice that GenericURLRequestJob::OnFetchComplete is computing an empty mime_type for http://example.com (which only had one html resource).
Looks like the tree is closed, but https://codereview.chromium.org/2501553003/ should fix this bug when it lands.
Project Member

Comment 4 by bugdroid1@chromium.org, Nov 15 2016

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

commit 1cf8ef72e2667c0b7df484fd906f95e7275e00f4
Author: alexclarke <alexclarke@chromium.org>
Date: Tue Nov 15 00:50:46 2016

Fix bug in HttpURLFetcher that dropped the response headers

BUG= 664989 

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

[modify] https://crrev.com/1cf8ef72e2667c0b7df484fd906f95e7275e00f4/headless/public/util/http_url_fetcher.cc

Status: Fixed (was: Available)

Sign in to add a comment