We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Each 5th invocation getting errors similar to the one below:
{ "errorMessage": "Protocol error (Runtime.enable): Target closed.", "errorType": "Error", "stackTrace": [ "Session._onClosed (/var/task/node_modules/puppeteer/node6/Connection.js:313:23)", "Connection._onClose (/var/task/node_modules/puppeteer/node6/Connection.js:168:15)", "emitTwo (events.js:106:13)", "WebSocket.emit (events.js:191:7)", "WebSocket.emitClose (/var/task/node_modules/ws/lib/WebSocket.js:224:10)", "_receiver.cleanup (/var/task/node_modules/ws/lib/WebSocket.js:210:41)", "Receiver.cleanup (/var/task/node_modules/ws/lib/Receiver.js:520:15)", "WebSocket.finalize (/var/task/node_modules/ws/lib/WebSocket.js:210:22)", "emitNone (events.js:91:20)", "Socket.emit (events.js:185:7)" ] }
Anyone seen this before?
NOTE: originally posted here: puppeteer/puppeteer#603 (comment)
The same 'one in five' error happens in on the serverless-chrome project as well as documented here: adieuadieu/serverless-chrome#41
The text was updated successfully, but these errors were encountered:
I also ran into this. Turns out, /tmp/ was full. There are some core.headless_shell.xx files left over after each execution.
/tmp/
core.headless_shell.xx
For now I'll be removing the file (only one generated per run) after each execution.
Sorry, something went wrong.
No branches or pull requests
Each 5th invocation getting errors similar to the one below:
Anyone seen this before?
NOTE: originally posted here: puppeteer/puppeteer#603 (comment)
The same 'one in five' error happens in on the serverless-chrome project as well as documented here: adieuadieu/serverless-chrome#41
The text was updated successfully, but these errors were encountered: