Skip to content
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

Closed
2 tasks
MarcusOtter opened this issue Apr 17, 2023 · 10 comments
Closed
2 tasks

[Bug]: STATUS_ACCESS_VIOLATION on youtube.com #10033

MarcusOtter opened this issue Apr 17, 2023 · 10 comments

Comments

@MarcusOtter
Copy link
Contributor

MarcusOtter commented Apr 17, 2023

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.

bild

Bug behavior

  • Flaky
  • PDF

Minimal, reproducible example

import puppeteer from "puppeteer";

(async () => {
	const browser = await puppeteer.launch({ headless: false });
	const page = await browser.newPage();
	await page.goto("https://youtube.com");
	const screenshot = await page.screenshot({ encoding: "base64" });
	console.log(screenshot);
	await browser.close();
})();

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

@MarcusOtter
Copy link
Contributor Author

MarcusOtter commented Apr 17, 2023

Also tried on Mac and versions 19.2.0...19.9.1 with the same result

@github-actions
Copy link

The issue has been labeled as confirmed by the automatic analyser.
Someone from the Puppeteer team will take a look soon!


Analyzer run

@OrKoN
Copy link
Collaborator

OrKoN commented Apr 17, 2023

Can confirm! Happens without using Puppeteer too:

path/to/Chromium --user-data-dir=/tmp/profile

@OrKoN
Copy link
Collaborator

OrKoN commented Apr 17, 2023

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.

@OrKoN OrKoN added the upstream label Apr 17, 2023
@OrKoN
Copy link
Collaborator

OrKoN commented Apr 17, 2023

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

@ggorlen
Copy link
Contributor

ggorlen commented Apr 26, 2023

Confirmed on 19.11.1. This Stack Overflow answer suggests downgrading to ^18.2.1.

@MarcusOtter
Copy link
Contributor Author

Thanks, I think I accidentally skipped testing 18.2.1. I tested with 18.1.0 and then 19.0.0. Will edit the question to make it more clear that 18.2.1 works fine.

@liynk
Copy link

liynk commented May 13, 2023

is it resolved?

@ggorlen
Copy link
Contributor

ggorlen commented May 19, 2023

@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.

@AnkitT0204
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants