alixaxel / chrome-aws-lambda

Chromium Binary for AWS Lambda and Google Cloud Functions
MIT License
3.17k stars 289 forks source link

[BUG] runtime.unhandledpromiserejection #300

Open raboomar opened 7 months ago

raboomar commented 7 months ago

c

Environment

Current Behavior

Currently works most of the time. I added logging, but it occasionally errors with " runtime.unhandledpromiserejection" when closing the browser. Usually, when the lambda is getting triggered multiple times

Error:

{ "errorType": "Runtime.UnhandledPromiseRejection", "errorMessage": "Error: Protocol error (IO.close): Target closed.", "reason": { "errorType": "Error", "errorMessage": "Protocol error (IO.close): Target closed.", "message": "Protocol error (IO.close): Target closed.", "stack": [ "Error: Protocol error (IO.close): Target closed.", " at /opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:217:63", " at new Promise ()", " at CDPSession.send (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:216:16)", " at Readable.read [as _read] (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/helper.js:281:30)", " at runMicrotasks ()", " at processTicksAndRejections (internal/process/task_queues.js:95:5)" ] }, "promise": {}, "stack": [ "Runtime.UnhandledPromiseRejection: Error: Protocol error (IO.close): Target closed.", " at process. (/var/runtime/index.js:35:15)", " at process.emit (events.js:412:35)", " at process.emit (domain.js:475:12)", " at processPromiseRejections (internal/process/promises.js:245:33)", " at processTicksAndRejections (internal/process/task_queues.js:96:32)" ] }

Steps to Reproduce