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.

Centos 7 - Unable to launch chromium

See original GitHub issue

I am getting below error in centos 7 and i tried many options on internet but nothing is working

Starting browser Unable to launch browser mode in sandbox mode. Lauching Chrome without sandbox. (node:7975) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! …/…/base/allocator/partition_allocator/partition_address_space.cc(41) Check failed: reserved_base_address_

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

at onClose (/home/xyz/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
at Interface.<anonymous> (/home/xyz/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
at Interface.emit (events.js:327:22)
at Interface.close (readline.js:424:8)
at Socket.onend (readline.js:202:10)
at Socket.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

(Use node --trace-warnings ... to show where the warning was created) (node:7975) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

** I tried every option on issue https://github.com/puppeteer/puppeteer/issues/2857 but nothing is working for me

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:13

github_iconTop GitHub Comments

3reactions
michaellwatsoncommented, Mar 31, 2021

This fixed it for me.

  1. Make sure all dependencies in package.json are up to date
  2. Install all the dependencies here https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md (one by one so none are missed)
  3. https://developers.google.com/web/tools/puppeteer/troubleshooting#setting_up_chrome_linux_sandbox including adding the path to bashrc
  4. Restart

For me it was already working on root, but not sub accounts, after following the instructions above, it works on sub accounts

0reactions
boardmaincommented, Nov 10, 2022

i did before open add a comment

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to launch chrome using puppeteer in Centos 7
Puppeteer runs very well in my other Centos7 installations but don't understand why it isn't working here. Please HELP! Node v12.20.1 Puppeteer ...
Read more >
Unable to launch chrome-42 in CentOS-6 - Google Groups
After updating Chrome to 42 version (on CentOS 6.6 ), i was unable to launch the chrome. It is simply dumping core. Filed...
Read more >
Google Chrome on a fresh CentOS 7.1 not starting up
Try to open google chrome as regular user. Do not try to open it as root user. You will not get this error...
Read more >
Can't get Google Chrome working in CentOS 7 - Page 2
Re: Can't get Google Chrome working in CentOS 7​​ Hi, I've had something similar with an automated build where both centos/epel7 and Google...
Read more >
How To Install Google Chrome on a RHEL/CentOS & Fedora
Open the Terminal application. Grab 64bit Google Chrome installer. · Install app and its dependencies on a CentOS/RHEL using the dnf command/yum ...
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