chromium: [BUG]: Error: Failed to launch the browser process!
Environment
chromium
Version: 106puppeteer
/puppeteer-core
Version: 18.2- Node.js Version: 16
- Lambda / GCF Runtime: AWS Lambda
Expected Behavior
Should work.
Current Behavior
2022-12-26T16:30:16.851Z fc7bd134-b96f-45f3-b681-961ec5abc5c9 INFO Error: Failed to launch the browser process!
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
at onClose (/var/task/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:299:20)
at Interface.<anonymous> (/var/task/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:287:24)
at Interface.emit (node:events:539:35)
at Interface.emit (node:domain:475:12)
at Interface.close (node:readline:586:8)
at Socket.onend (node:readline:277:10)
at Socket.emit (node:events:539:35)
at Socket.emit (node:domain:475:12)
at endReadableNT (node:internal/streams/readable:1345:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Steps to Reproduce
Followed same steps as in doc
Possible Solution
Any guide to debug ? Also, I am using Typescript.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (5 by maintainers)
@twistypigeon Would you mind sharing how you rebuilt your chromium package? I’m currently encountering the same issue as you with the exact same package versions. Thank you!
I was able to change some settings and fix this error. I apologize for the inconvenience caused. I found that setting arm64 as the architecture failed; setting it to x86_64 made it work with both Node.js 16 and 18.