-
-
Notifications
You must be signed in to change notification settings - Fork 69
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] Unable to open page with disabled setGraphicsMode #247
Comments
Interestingly, if setting So this setup only works with Node 18 and with graphics mode disabled: {
"dependencies": {
"puppeteer-core": "^19.8.5"
},
"devDependencies": {
"@sparticuz/chromium": "^112.0.2"
}
} And this one works well on Node 20 with both graphics modes: {
"dependencies": {
"puppeteer-core": "^22.4.1"
},
"devDependencies": {
"@sparticuz/chromium": "^122.0.0"
}
} For us, the graphics mode makes the crawler twice slower. Our script normally finishes in 7.5-8.5 seconds, with the graphics mode enabled it takes 15-18 seconds. |
|
Until this bug gets fixed, I'm going to disable turning off accelerated graphics |
Sorry for the delay, there were other issues with 126 that needed to get fixed. This is now live, however, I'm going to keep the bug open. |
* master: 126.0.0 don't disable the graphics stack #247 update to chromium 126 ignore internal docker folder update deps
Once
chromium.setGraphicsMode = false;
open page times out.Environment
chromium
Version: 123puppeteer
/puppeteer-core
Version: 22.6.1Expected Behavior
Chromium 112 worked well, disabling graphics mode effectively reducing the launch time by 25-30%.
Current Behavior
Opening a new page freezes forever.
Steps to Reproduce
Once
setGraphicsMode
is commented out things get back to life again.The text was updated successfully, but these errors were encountered: