-
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]: STATUS_ACCESS_VIOLATION on youtube.com #10033
Comments
Also tried on Mac and versions |
The issue has been labeled as confirmed by the automatic analyser. |
Can confirm! Happens without using Puppeteer too:
|
It does not happen on a ToT Chromium binary I built locally so it should be fixed when the next release of Chromium is integrated into Puppeteer. |
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/1131172/ works but it will be some time till we roll next release of Chromium |
Confirmed on 19.11.1. This Stack Overflow answer suggests downgrading to |
Thanks, I think I accidentally skipped testing |
is it resolved? |
@liynk According to this comment, it's resolved as of 20.0.0, and I've confirmed that it works on one YT page that crashed on 19.11.1. Ideally we could link a PR and close this issue but I don't have time at the moment to dig around. |
what is the solution of this bug can you please help me right now i am using pupptteer version 16.7 and i am not able to find out the reason why it is coming and how to resolve it |
Bug expectation
All puppeteer versions after
v18.2.1
give me a STATUS_ACCESS_VIOLATION when trying to access youtube.com (both headless and headful). v18.2.1 and version prior do not seem to give me this error.Current workaround: Downgrade to
v18.2.1
.Bug behavior
Minimal, reproducible example
Error string
Navigation timeout of 30000 ms exceeded
Puppeteer configuration
No response
Puppeteer version
19.9.1
Node version
18.16.0
Package manager
npm
Package manager version
8.4.1
Operating system
Windows
The text was updated successfully, but these errors were encountered: