Issue metadata
Sign in to add a comment
|
Detect when starting with too little shared memory space
Reported by
potoms....@gmail.com,
Feb 26 2017
|
||||||||||||||||||
Issue descriptionChrome Version : 58.0.3018.3 URLs (if applicable) : http://li-bracelet.com/ Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox: IE: What steps will reproduce the problem? This happens only when running --headless chrome in a container. I used a modified version of yukinying/chrome-headless-browser:58.0.3018.3 (https://hub.docker.com/r/yukinying/chrome-headless-browser/) to enable crash dumps. It happens when visiting http://li-bracelet.com/ in the devtools. The page starts loading, then crashes when almost loaded. Seems to always happen on the analytics script. I see the same when trying to load it through the remote debugging protocol and it ends with a Inspector.targetCrashed event right after the analytics script is downloaded. I was able to generate a crash dump which I attached to this issue. Please provide any additional information below. Attach a screenshot if possible. I tried reproducing with the same chrome version on linux and can't reproduce the crash that way. If necessary I think I can find more urls that produce this issue
,
Feb 27 2017
The problem is caused by insufficient shm memory and would not be reproducible if the container is started with "--shm-size=1024m". Yet it would be nice if chrome is able to give useful hint for "Bus Error" caused by insufficient shm memory.
,
Feb 27 2017
,
Feb 27 2017
Seems like we could add a nicer error message for this.
,
Mar 10 2017
,
May 15 2017
,
May 17 2017
Do you know how to catch this error using nodeJs chrome-remote-interface and a docker container chrome headless ? My script crashes because of this error but i get trouble to detect it in using devtools-protocol API and re-launch a container.
,
May 17 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Feb 27 2017