Chrome 129 headless Error

Question

Chrome 129 headless Error

Closed this issue 2 months ago · 12 comments

magdev2022 commented 4 months ago

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.

Answer 1 · 2024-09-18T10:57:16.000Z

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

Answer 2 · 2024-09-19T01:07:23.000Z

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

Answer 3 · 2024-10-01T21:57:20.000Z

Do you know how to fix this issue interim?

Answer 4 · 2024-10-02T13:19:25.000Z

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

Answer 5 · 2024-10-03T13:28:57.000Z

Yes we are using installed browser

Answer 6 · 2024-10-03T14:21:30.000Z

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

Answer 7 · 2024-10-03T14:34:54.000Z

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.

Answer 8 · 2024-10-03T14:36:21.000Z

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

Answer 9 · 2024-10-07T12:47:16.000Z

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.

Answer 10 · 2024-10-07T12:49:00.000Z

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.

Answer 11 · 2024-10-16T08:57:10.000Z

This is resolved in google chrome release - Version 130.0.6723.59

Answer 12 · 2024-10-25T21:47:57.000Z

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?