Chrome browser disconnect and execution restarts #8367
Labels
STATE: Need response
An issue that requires a response or attention from the team.
TYPE: bug
The described behavior is considered as wrong (bug).
What is your Scenario?
There is a corner case issue happening due to the combination:
The following is observed when the automation script reaches the publish campaign stage (the root cause is not clear, for sure it happens a few steps before Publish, but it is most obvious in the UI after Publish):
1/ Chrome browser "freezes". It looks the same as if JS is disabled from the browser dev-tool options. This is visible in the UI because the Publish confirmation popup "Campaign Saved successfully" does not disappear (it should disappear after a couple of seconds)
There are no console errors in the Chrome instance pointing to anything unusual
Network calls (ajax calls from our app) keep coming through.
2/ DEBUG=testcafe:* -> after 3 min, we see "browser disconnect +3m" in the console
There is no other error or anything suspicious in the debug logs.
3/ TestCafe restarts the execution all over from the beginning. Please note quarantine mode is not enabled
4/ steps 1 to 3 are repeated 3 times until finally the executions stops giving the very generic Browser disconnect error
NOTE 1:
Issue is not OS related. We are reproducing it on Ubuntu and MacOS.
NOTE 2:
When we change the browser to Firefox or Safari - the exact same test script passes successfully without any issues.
What is the Current behavior?
Chrome browser disconnects, execution is restarted when it should not
What is the Expected behavior?
Test passes on Chrome like it does on Firefox.
What is the public URL of the test page? (attach your complete example)
N/A cannot provide due to security.
What is your TestCafe test code?
N/A cannot provide due to security.
Your complete configuration file
No response
Your complete test report
No response
Screenshots
Sending a video of the execution
TestCafe_Chrome_Disconnect.mp4
Steps to Reproduce
As per the video
TestCafe version
3.7.0, 3.7.1
Node.js version
20.10
Command-line arguments
n/a
Browser name(s) and version(s)
Chrome 131, Chrome 132, Chromium 134.0.6970.0, Chromium 113.0.5637.0
Platform(s) and version(s)
Mac OS 15.2, Ubuntu 20.04
Other
We totally understanding that it is impossible for you to debug with the provided information.
We are hoping to organise a debug session over zoom or another tool.
We are OK also to install some "debug" testcafe version that could give more insights as to what is happening.
Although there is a workaround with Firefox, this is not a desirable long term solution for us, because there are other problems arising from using Firefox.
Thank you in advance!
The text was updated successfully, but these errors were encountered: