-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Bug]: An Error Occurred on the Page Due to Code Execution #12439
Comments
This issue was not reproducible. Please check that your example runs locally and the following:
Once the above checks are satisfied, please edit your issue with the changes and we will |
could you obtain the crash id from chrome://crashes (you might need to re-user the userDataDir for that)? |
Is it reproducible with the bundled Chrome for Testing version? |
Able to reproduce with stable and canary versions. |
Chrome: crash id: |
one-script repro |
Minimal, reproducible example
Error string
Crash Page: STATUS_ACCESS_VIOLATION
Bug behavior
Background
Chrome: windows x64 124.0.6367.201
When the above code is running, it causes a crash on the page.
Expectation
It was supposed to write the popup address to the console and then close it.
Reality
Unfortunately, crashes occurred on both the page and the popup, and the popup listener did not function as intended.
Puppeteer configuration file (if used)
No response
Puppeteer version
22.8.1
Node version
v21.7.1
Package manager
npm
Package manager version
10.6.0
Operating system
Windows
The text was updated successfully, but these errors were encountered: