question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: kill ESRCH on puppeteer.launch({}) on CircleCI

See original GitHub issue

Steps to reproduce

Tell us about your environment:

  • Puppeteer version: 0.13.0
  • Platform / OS version: Ubuntu on CircleCI
  • Node.js version: 8.9.1

What steps will reproduce the problem? Not sure how to repro this. Maybe try launching puppeteer on CircleCI via npm test? This works fine locally on OSX.

It fails on the following call: const browser = await puppeteer.launch({})

What is the expected result? Puppeteer launch call is successful

What happens instead?

[1] Setup Puppeteer Environment.
[1] Error: kill ESRCH
[1]     at Object._errnoException (util.js:1024:11)
[1]     at process.kill (internal/process.js:183:18)
[1]     at forceKillChrome (/home/circleci/repo/node_modules/puppeteer/lib/Launcher.js:162:19)
[1]     at killChrome (/home/circleci/repo/node_modules/puppeteer/lib/Launcher.js:147:9)
[1]     at Function.launch (/home/circleci/repo/node_modules/puppeteer/lib/Launcher.js:137:7)
[1]     at <anonymous>
[1]     at process._tickCallback (internal/process/next_tick.js:188:7)
[1] jest --config ./src/jest.config.js exited with code 1

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

5reactions
theoutlandercommented, Jan 17, 2018

@TrySound here is my circle config: https://circleci.com/gh/theoutlander/testerbot/45#config/containers/0

You might be able to find more details from my project source @ https://github.com/theoutlander/testerbot/tree/master/src

I just noticed I passed in additional params as I was fiddling to solve this issue, so not sure if that worked in combination with the docker build.

const browser = await puppeteer.launch({
    args: ['--no-sandbox', '--disable-setuid-sandbox']
})
3reactions
EJTHcommented, Mar 2, 2018

Hi! Here is how I got it running under WSL:

install chromium browser through apt-get

$ sudo apt-get install chromium-browser

then:

const browser = await puppeteer.launch({executablePath:'/usr/bin/chromium-browser'});

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unhandled promise rejection (rejection id: 1): Error: kill ESRCH
I installed Node and Puppeteer with Windows 10 Ubuntu Bash, but didn't manage to make it work, yet I manage to make it...
Read more >
Inquiry failed with Puppeteer error “kill ESRCH” (#43) · Issues ...
Inquiry failed with Puppeteer error “kill ESRCH”. Error: internal/process.js:188 throw errnoException(err, 'kill'); ^ Error: kill ESRCH at exports.
Read more >
Nytro's Content - Page 50 - Romanian Security Team
For example to generate the system error code 3. On Linux. /* 0x03 == ESRCH == No such process */ void generate_error_3() {...
Read more >
[SOLVED] Python Netlink Multicast Communication in Kernels ...
I'm not very fluent with Python, so use this only as a starting point ... By the way: When nlmsg_multicast() throws ESRCH ,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found