Puppeteer broken on Ubuntu 18.04 after upgrade & restart

The exact same setup worked a few hours ago. I’ve ran apt-get full-upgrade and it fails to run anymore. Not sure what exactly it is related to. Running in docker from latest.

Update: I was able to reproduce this on another Ubuntu 18.04 with the same kernel version. It worked fine with Linux kernel 4.15! This means that this might be a problem with chrome itself, not puppeteer - please confirm.

Update: Works fine with 5.0.0-25-generic but fails on 5.0.0-27-generic.

Steps to reproduce

Tell us about your environment:

• Puppeteer version: docker image buildkite/puppeteer:23a2e145eb22
• Platform / OS version: Ubuntu 18.04.03, Linux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP
• Node.js version: v10.15.3 (bundled in the docker image)

const puppeteer = require('puppeteer');
puppeteer.launch({
  args: [
    '--disable-setuid-sandbox',
    '--no-sandbox',
    '--disable-dev-shm-usage',
  ],
})
  .then(async browser => {
    const page = await browser.newPage();
    await page.goto('https://example.com');
    // await page.screenshot({ path: '/app/screenshot.png' });
    // await browser.close();
  })
  .catch(e => {
    console.log(e);
  });

$ docker run -it -v $(pwd):/app -u node -w /app buildkite/puppeteer node test.js
Error: Navigation failed because browser has disconnected!
    at CDPSession.LifecycleWatcher._eventListeners.helper.addEventListener (/node_modules/puppeteer/lib/LifecycleWatcher.js:46:107)
    at CDPSession.emit (events.js:189:13)
    at CDPSession._onClosed (/node_modules/puppeteer/lib/Connection.js:215:10)
    at Connection._onClose (/node_modules/puppeteer/lib/Connection.js:138:15)
    at WebSocketTransport._ws.addEventListener.event (/node_modules/puppeteer/lib/WebSocketTransport.js:45:22)
    at WebSocket.onClose (/node_modules/ws/lib/event-target.js:124:16)
    at WebSocket.emit (events.js:189:13)
    at WebSocket.emitClose (/node_modules/ws/lib/websocket.js:191:10)
    at Socket.socketOnClose (/node_modules/ws/lib/websocket.js:850:15)
    at Socket.emit (events.js:189:13)
  -- ASYNC --
    at Frame.<anonymous> (/node_modules/puppeteer/lib/helper.js:110:27)
    at Page.goto (/node_modules/puppeteer/lib/Page.js:629:49)
    at Page.<anonymous> (/node_modules/puppeteer/lib/helper.js:111:23)
    at puppeteer.launch.then (/app/test.js:12:16)
    at process._tickCallback (internal/process/next_tick.js:68:7)

$ uname -a
Linux cascara 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic

$ docker -v
Docker version 19.03.2, build 6a30dfc

$ docker image ls | grep puppeteer
buildkite/puppeteer   latest              23a2e145eb22        4 months ago        830MB

$ docker run -it -v $(pwd):/app -u node -w /app buildkite/puppeteer node -v     
v10.15.3

The same script (same flags) worked before the upgrade & reboot.

[mikk351]

puppeteer.launch({ args: [ '--single-process' ]} Seems to fix the issue for me, running ubuntu 5.0.0-27-generic

[stale[bot]]

We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!