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
Puppeteer fails with Chromium 72.0.3626.96 #4040
Comments
Same here, met this exception right after updating to Chromium 72.0.3626.96 |
Same error message in my CI pipeline. |
@mateusbs17 @dr-dimitru @rasca looks like the new chromium fails to launch on your host system. Can you try running it manually - does it launch? |
@aslushnikov yes, it runs perfectly, with and without flags we pass to Chromium via puppeteer |
@dr-dimitru so the only difference here is that it's spawned from-inside node.js process? |
@aslushnikov yes, by puppeteer |
For me it happens inside a docker instance when I run
with this flags in my karma.conf.js
|
JFTR, for the setup described by mateusbs17 we fixed it by upgrading to Chromium 72.0.3626.122, there appears to be a regression in Chromium releases >= 72.0.3626.96 and < 72.0.3626.122 which broke --remote-debugging-port. Not closing the task yet, but maybe others affected by this regression could re-test their setups as well. |
I can confirm that the --remote-debugging-port flag is causing these errors. Chromium 75.0.3765.0 is also broken. remove it and things work fine, except you have a heck of a time debugging. Any chance puppeteer can upgrade the chromium version? |
@govindrai can't remove it, we use and need it. |
I've got a similar error with Chromium 73.0.3683.75
In my case adding the flag |
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! |
Hello everyone, I am working on a Wikimedia project called chromium render (a.k.a Proton) and we use Debian stretch and its stable channel to run chromium. Recently we had an issue registered after Debian library upgrade to 72.0.3626.96-1~deb9u1.
Now we got the following error when trying to instantiate chromium inside a job queue:
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
I set up a Docker environment to test it:
What is the expected result?
What happens instead?
With the right matching versions between puppeteer and chromium the service works fine. You can reproduce them following steps above with the repos below:
Thanks in advance.
The text was updated successfully, but these errors were encountered: