Hi there,
Just suddenly, using k6 browser 0.51, 0.52 or 0.52, latest Chrome browser, random test execution become frozen at random point and the execution fails for no reason.
Could this be Chrome issue? I am sure no changes were made to provoke this.
This is happening for 20 days already, and just once it worked to complete the test run.
Whenever I try executing from the local or CI, I could see that browser Chrome become frozen literally with loading wheel on the mouse cursor, so no idea what could cause it. Tested through 0.51 0.52 and 0.53 versions, updated tests to use k6/browser, but the same is also when using experimental.
This smells more like a Chrome issue?
Hi,
It might because of the browser module, Chromium, the website under test, or your scripts. We can’t be sure of without looking at your script and the website. Please send me a private message so that I can look into it.
Thanks.
Hey @inancgumus
The script didnt change for a while, this has started just suddenly.
The plugin we are testing against changed, but then I tried against older versions and it was the same.
The data on the test site did not change.
If it is browser module, how can I test this more to make sure it is browser module? I tried using -1 older k6 version.
Yes, you can try it with older versions and see if the issue still occurs. Please let us know afterward. Thanks!
It is still occuring even with 0.50 k6 and since I am testing a WordPress plugin, I tried against older plugin’s versions… but the issue with frozen Chrome browser window occurs also when just logging to WordPress site (while executing test of course, not manually) so the only one left way to test if it’s about maybe WordPress is to test against older WP version.
Possibly, the issue may be the Chrome browser (testing with the latest version) so I will try some older browser versions.
Worth mentioning that only 1 test run succeeded in a 1 month of nightly tests. So that’s weird as well.
Hi @inancgumus
I can confirm that the issue with frozen browser window doesn’t occur on Chrome (Mac) from 2022 (I was unable to find chrome version just before this issue started, before 6th August). It seems that there is an issue between k6 (any version) and Chrome after this update 129.0.6628.3
from 6th August.
It also seems they (Chrome) had 5 updates that day 6th August, and all further updates contained that frozen issue except only 23rd August.
Is this something k6 can fix or deal with Chrome?
I am happy to help and assist with anything.
Thanks for the detailed explanation. This seems like a valid issue. Could you kindly create one here? Please include as many details as possible as you did above. Once you create the issue, please feel free to come up with a PR (if you desire). We’re always open to contributions. Thanks!
1 Like