-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
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
stack_overflow using puppeteer #106
Comments
Can confirm it is occurring either on the goto function call, or the subsequent delay call |
Check this comment. Let me know if it solves your issue. |
I had looked into that issue as well, but nowhere am I using the evaluate function. I look into a few of the puppeteer functions but I couldn't find any usage there either. |
Further research indicating that this is happening on request interception. Trying to narrow it down if its from request continue/abort or that I'm handling the function asynchronously. |
The README file should be updated to reflect this issue. Closing now as there is nothing that we can do to fix puppeteer (or electron too). It seems that the async arrow functions cause a crash whenever two contexts come into contact (node.js with electron, or node.js with puppeteer). This is definitely a C++ bug that most likely should be fixed in v8 itself. |
Error
Code Snippit
Steps to reproduce:
Environment:
Win10 x64
Node v14.15.5
"puppeteer": "^5.5.0",
"puppeteer-extra": "^3.1.17",
"puppeteer-extra-plugin-stealth": "^2.7.5", // I disabled this and error still occurs.
"puppeteer-extra-plugin-user-data-dir": "^2.2.11"
I did find some similar issues such as #57
I'll do some more digging with puppeteer to see if it is using the Function prototype anywhere, but I'm not sure yet if that's the case here.
Great project btw.
The text was updated successfully, but these errors were encountered: