Crashes on Docker with emulated-form-factor=desktop

Provide the steps to reproduce

1. Use this Dockerfile
2. Run LH with --emulated-form-factor=desktop and “heavy js page” like amazon.fr

Dockerfile:

FROM node:12.4-alpine

RUN apk add --update --no-cache chromium && rm -rf /var/cache/apk/*

docker-compose.yml

version: '3.5'

services:

  lh:
    build:
      context: ./docker/nodejs
    tty: true
    working_dir: /app
    volumes:
      - ./:/app

Note:

• Same issue on many Dockerfiles (node:10*-alpine, node:10-slim, node:12-slim), using chromium or chrome…
• No crash on my computer: Node 12 on Debien Stretch

What is the current behavior?

Inside docker shell:

./node_modules/.bin/lighthouse --emulated-form-factor=desktop --chrome-flags="--no-sandbox --headless --disable-gpu" https://www.amazon.fr/
  ChromeLauncher Waiting for browser. +0ms
  ChromeLauncher Waiting for browser... +0ms
  ChromeLauncher Waiting for browser..... +506ms
  ChromeLauncher Waiting for browser.....✓ +4ms
  status Connecting to browser +88ms
  status Resetting state with about:blank +11ms
  status Benchmarking machine +36ms
  status Initializing… +506ms
  status Resetting state with about:blank +32ms
  status Setting up network for the pass trace +35ms
  status Cleaning browser cache +2ms
  status Beginning devtoolsLog and trace +12ms
  status Loading page & waiting for onload CSSUsage, ViewportDimensions, RuntimeExceptions, ConsoleMessages, AnchorElements, ImageElements, LinkElements, MetaElements, ScriptElements, AppCacheManifest, Doctype, DOMStats, OptimizedImages, PasswordInputsWithPreventedPaste, ResponseCompression, TagsBlockingFirstPaint, FontSize, EmbeddedContent, RobotsTxt, TapTargets, Accessibility +3ms
  Driver:warn Timed out waiting for page load. Checking if page is hung... +45s
  Driver:warn Page appears to be hung, killing JavaScript... +1s
  status Disconnecting from browser... +30s
  ChromeLauncher Killing Chrome instance 416 +8ms
Runtime error encountered: Waiting for DevTools protocol response has exceeded the allotted time. (Method: Emulation.setScriptExecutionDisabled)
LHError: PROTOCOL_TIMEOUT
    at Timeout._onTimeout (/usr/local/lib/node_modules/lighthouse/lighthouse-core/gather/driver.js:399:21)
    at listOnTimeout (internal/timers.js:531:17)
    at processTimers (internal/timers.js:475:7)

What is the expected behavior?

No crashes with --emulated-form-factor=mobile

Environment Information

• Lighthouse version: 4.0/4.1
• Node.js version: 10/12.1/12.4
• Operating System: Debian Stretch with Docker 18.09.1

[felipe-vieira]

I’ve had the same issue and found a workaround. Apparently, chrome relies on shared memory which is mounted on /dev/shm, my alpine image default partition has only 64mb, so I had to mount it to a host volume: added the following to my docker-compose file:

services:
  lighthouse:
    volumes:
      - lighthouse-shm:/dev/shm
...
volumes:
  siteanalysis-dashboard-data:

After the volume is mounted, lighthouse completes normally.

[patrickhulce]

I was unable to reproduce this issue with https://github.com/GoogleChrome/lighthouse/issues/9212#issuecomment-607276050 or --disable-dev-shm-usage so we’ll consider that the solution here 👍