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

Chrome 129 headless Error #2782

Closed
magdev2022 opened this issue Sep 18, 2024 · 12 comments · Fixed by #2811
Closed

Chrome 129 headless Error #2782

magdev2022 opened this issue Sep 18, 2024 · 12 comments · Fixed by #2811

Comments

@magdev2022
Copy link

magdev2022 commented Sep 18, 2024

Today, I updated the Chrome browser to the latest version (129).
After the update, running Chrome in headless mode produces an unusual result: a blank white window appears, matching the size of the browser.
image

@kblok
Copy link
Member

kblok commented Sep 18, 2024

We don't have support for 129 yet. Upstream change in puppeteer might come soon.

@magdev2022
Copy link
Author

I tested on chrome128 and chrome130. there was no problem. I think chromium(129) has a problem.

@vmeganathan81
Copy link

Do you know how to fix this issue interim?

@kblok
Copy link
Member

kblok commented Oct 2, 2024

So you are using your installed browser rather than the one downloaded by puppeteer right?

@vmeganathan81
Copy link

Yes we are using installed browser

@kblok
Copy link
Member

kblok commented Oct 3, 2024

I tried to reproduce that. But I'm not getting that on Chrome 129.0.6668.60 on MacOS.

@kblok
Copy link
Member

kblok commented Oct 3, 2024

It seems this was reported on Selenium here. It was also reported on chromium bugs here.

One potential, an ugly, workaround is to add this command line argument --window-position=-2400,-2400.

@kblok
Copy link
Member

kblok commented Oct 3, 2024

It is also reported that you could replace Headless = false with HeadlessMode = HeadlessMode.Shell.

@jaydeep009
Copy link

It is also reported that you could replace Headless = false with HeadlessMode = HeadlessMode.Shell.

That is not correct way, since that will point to old headless mode which is going to be out of support from chrome soon.
By default parameters, i.e new headless we are getting this white screen.

@kblok
Copy link
Member

kblok commented Oct 7, 2024

It is also reported that you could replace Headless = false with HeadlessMode = HeadlessMode.Shell.

That is not correct way, since that will point to old headless mode which is going to be out of support from chrome soon. By default parameters, i.e new headless we are getting this white screen.

Ok so you'll need to wait till the chromium team fixes the bug.

@jaydeep009
Copy link

This is resolved in google chrome release - Version 130.0.6723.59

@CaCTuCaTu4ECKuu
Copy link
Contributor

Can confirm that current build as of 26 Oct 2024 have this issue
I'm running next code

var browserFetcher = new BrowserFetcher();
await browserFetcher.DownloadAsync()
    .ConfigureAwait(false);

var launchOptions = new LaunchOptions()
{
    Args = new string[]
    {
        "--no-sandbox"
    },
    Headless = true
};
browser = await Puppeteer.LaunchAsync(launchOptions).ConfigureAwait(false);

Fetching loads Chrome/129.0.6668.100

  • Windows 11 23H2 (22631.4317)
  • net6.0

Waiting for new PuppeteerSharp version?

stesee added a commit to Codeuctivity/PuppeteerSharp.Renderer that referenced this issue Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants