Open gyloh9210 opened 4 years ago
Sometimes I get a similar error, which I can't reproduce. It's caught via process.on('unhandledRejection', ...)
, but after it happens, the cluster seems to stop working (looks like cluster.execute
returns promises that stay pending).
Unhandled Rejection at: Promise Promise {
<rejected> TimeoutError: Timed out after 30000 ms while trying to connect to the browser! Only Chrome at revision r768783 is guaranteed to work.
at Timeout.onTimeout ([...]\node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:204:20)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
}
I see the same error when using --single-process
on MacOS 10.15.7 (Catalina) on a MBP 16" (Intel). It's random.
Hi i am unable to run my source code in ubuntu 20.04. Here is my source code.
And I got these errors.
(node:63559) UnhandledPromiseRejectionWarning: Error: Unable to get browser page at Worker.<anonymous> (/var/www/web-scrapper/node_modules/puppeteer-cluster/dist/Worker.js:44:31) at Generator.next (<anonymous>) at fulfilled (/var/www/web-scrapper/node_modules/puppeteer-cluster/dist/Worker.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:63559) 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) (node:63559) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Please help.