Network.dataReceived stalls when navigating to large image via docker container (debian) using chrome-remote-interface
Reported by
baerl...@gmail.com,
Jun 8 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Using this dockerfile: https://bitbucket.org/snippets/isave/jL4RM And this test nodejs script which uses chrome-remote-interface: https://bitbucket.org/snippets/isave/gnz8p npm install chrome-remote-interface sleep-promise 2. docker build -t test 3. docker run test What is the expected behavior? Script finishes, and Page.loadEventFired is written to the console. What went wrong? Multiple lines of "Network.dataReceived" are written to the console, but the script hangs. Did this work before? No Chrome version: 60.0.3112.20-1 Channel: dev OS Version: debian:sid (Docker) Flash Version: Issue at chrome-remote-interface: https://github.com/cyrus-and/chrome-remote-interface/issues/147 This seems to be related to chrome running in docker. Developer(@cyrus-and) of chrome-remote-interface is unable to reproduce when running via a Debian box (no docker) If pointing to a smaller image in Page.navigate, and the script works as expected.
,
Jun 9 2017
This issue seems to be out of TE-scope. Hence, adding label TE-NeedsTriageHelp for further investigation. Thanks...!!
,
Jun 9 2017
You may close this as it is related to the shared memory issue mentioned here: https://bugs.chromium.org/p/chromium/issues/detail?id=522853 Docker uses a default size for /dev/shm set to 64Mb, which is too small for chrome headless. Increasing the size of /dev/shm solved my issue.
,
Jun 9 2017
As per comment#3, closing this issue as 'Wontfix'. Please feel free to file chrome related issues if you find any. Thanks..!! |
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted