You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run my code through pm 2, after the next restart (pm2 restart) none of the clients connected, when trying to restart a separate client, only initialize happens and that's it
the memory on the server was increased even before this incident, also after this problem I tried to pass an argument
puppeteer: {args: [ "--shm-size=3gb",]},
but unsuccessfully
I attach the client creation code
Puppeteer version
10.4.0
Node.js version
v15.8.0
npm version
7.5.1
What operating system are you seeing the problem on?
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days.
We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!
Bug description
Steps to reproduce the problem:
I run my code through pm 2, after the next restart (pm2 restart) none of the clients connected, when trying to restart a separate client, only initialize happens and that's it
the memory on the server was increased even before this incident, also after this problem I tried to pass an argument
puppeteer: {args: [ "--shm-size=3gb",]},
but unsuccessfully
I attach the client creation code
Puppeteer version
10.4.0
Node.js version
v15.8.0
npm version
7.5.1
What operating system are you seeing the problem on?
Linux
Relevant log output
"Protocol error (Runtime.callFunctionOn): Target closed."
The text was updated successfully, but these errors were encountered: