Tests started hanging randomly after upgrading to Chrome 130 + TestCafe 3.7.0-rc.1

[thomas-jakemeyn]

What is your Scenario?

We run 170+ TestCafe tests in Chrome headless within Docker. They used to be executed reliably in about 15 minutes in Chrome 129. After the upgrade to Chrome 130 + TestCafe 3.7.0-rc.1 (which solves #8286), the same tests now execute in about 30 minutes. After looking at the logs, we realised that some of them (but not always the same) seem to hang randomly.

Note that we don't use the spec reporter (see #8307). Also, we pass the following command line switches to Chrome:

--disable-fre --no-default-browser-check --no-first-run --disable-search-engine-choice-screen

What is the Current behavior?

Tests hang randomly in Chrome 130 whereas they used to be executed reliably in Chrome 129.

What is the Expected behavior?

Tests should not hang randomly in Chrome 130.

What is the public URL of the test page? (attach your complete example)

NA

What is your TestCafe test code?

NA

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

NA

TestCafe version

3.7.0-rc.1

Node.js version

No response

Command-line arguments

NA

Browser name(s) and version(s)

Chrome 130

Platform(s) and version(s)

Ubuntu 24.04 (Docker)

Other

No response

[thomas-jakemeyn]

I just checked usage of CPU, disk and memory during test execution and everything seems perfectly fine. So the problem is apparently not related to a lack of resources.

[thomas-jakemeyn]

I tested with Chrome 130 + TestCafe 3.6.2 patched with a backport of this change and the behaviour is the same.

[ayemelyanenko-chegg]

I am also seeing this issue even without upgrading to TestCafe RC 3.7.0. The tests hang with --disable-native-automation and Chrome 130 and version 3.6.2. The issue seems to be with this specific Chrome version 130.0.6723.69-1 which was released today, on October 22nd and that's when the issues started to happen. Seems to also happen on ubuntu/debian images.

[Bayheck]

Hello,
Thank you for reaching out to us.

Could you tell if the issue is similar to #8308?

Or do the tests hang but still pass?

[thomas-jakemeyn]

It is a different issue because we have a retry mechanism and tests end up passing.

[joshuaegclark-rally]

Not entirely sure what changed, but I am now having tests hang when running with TestCafe 3.7.0-rc.1 and Chrome 130.0.6723.59 on macOS Sonoma 14

The error in question is "Error in Role initializer" "Error: WebSocket is not open: readyState 3 (CLOSED)"

[ayemelyanenko-chegg]

As a workaround, if you have Microsoft Edge installed, you can use that for your tests for now as Edge is Chromium based

[Bayheck]

Hello,

We have released TestCafe 3.7.0-rc.2, which addresses this issue. Please try it and let us know if the issue is gone.

[thomas-jakemeyn]

@Bayheck, problem solved, thank you!