Issue metadata
Sign in to add a comment
|
Network filmstrip hangs at "Fetching frames..." when running headless in a docker container
Reported by
lawn...@gmail.com,
Feb 6 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Install Docker 2. docker build -t google-chrome-unstable . 3. docker run --privileged -it -p 9222:9222 google-chrome-unstable /bin/bash 4. (in the docker container) google-chrome-unstable --headless --disable-gpu --remote-debugging-port=9222 --remote-debugging-address=0.0.0.0 --window-size=412,732 https://www.google.com 5. Open http://localhost:9222 in your browser and click "Google" 6. Select "Network" tab in developer tools 7. Click the camera icon to enable filmstrip capture 8. Hit the keyboard combo (Cmd-R on OS X, Ctrl-R on Linux) to reload and capture filmstrip What is the expected behavior? Filmstrip of the page load is captured and displayed What went wrong? The words "Fetching frames..." is displayed but no frames are ever shown. Did this work before? Yes 57.0.2987.19 dev Chrome version: 58.0.3000.4 dev Channel: dev OS Version: Ubuntu 16.04.1 Flash Version: N/A
,
Feb 7 2017
,
Feb 7 2017
,
Feb 7 2017
Looks like this cannot triaged from chrome TE-end, adding "TE-NeedsTriageHelp" label for further triage
,
Feb 7 2017
Will, please take a look.
,
Feb 7 2017
,
Feb 8 2017
I should mention that the Docker host is OS X 10.12.3 (16D32)
,
Feb 20 2017
,
May 15 2017
,
May 24 2017
Removing from bisect bucket since TE cannot repro.
,
Nov 13 2017
No repro |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lawn...@gmail.com
, Feb 6 2017