ECONNRESET on Chrome/Chromium 117.0.5851.0 when using Cypress <12.15.0 or passing--headless=old in browser launch options
#27804
Comments
|
Let me know if you guys feel this is more of a chrome/chromium issues and I can close. |
|
Are there any known workarounds? |
|
Same issue here, had to downgrade to 116 version to make it works |
|
A colleague reported the same issue. Will watch to see how things go |
|
We’re investigating this issue currently. |
|
Running on Ubuntu 22.04.03 LTS I'm seeing Chrome 117.0.5938.62-1 (google-chrome-stable) crashing with SIGSEGV if arg is reset from |
|
If anyone is seeing this issue on Cypress versions 12.14.0 and earlier and can use the setupNodeEvents(on, config) {
on('before:browser:launch', (browser, launchOptions) => {
if (browser.name === 'chrome' && browser.isHeadless) {
launchOptions.args = launchOptions.args.map((arg) => {
if (arg === '--headless') {
return '--headless=new'
}
return arg
})
}
return launchOptions
})
} |
|
Should we make a bug report to Chromium? @jennifer-shehane @MikeMcC399 @mschile |
|
I was able to further drill into which version caused the issue.
I want to check on a few more things and then I'll probably log an issue to Chromium and post back here with the link. |
|
@mschile I can confirm that
|
|
I was able to reproduce the issue outside of Cypress in standalone Chrome. I've logged a Chromium bug. |
Good to see you've logged a bug! Did you also test using the parameter According to - Chrome Developer > Try out the new Headless I would expect both
to work, since there hasn't been any announcement that these parameters are unsupported, even though they do write:
|
|
@MikeMcC399 I tested on my Windows machine with --headless and it has the same issue as --headless=old, I'll make a new comment on the bug report |
Thank you @alexsch01 for confirming and following up in the Chromium bug report! |
|
This is how I explained it in the bug report comments
|
|
Your comments make the problem now very clear! 👍🏻 The worst impact is that failing to accept |
|
It seems to me that we didn't catch this Chromium bug before Chrome 117 went stable most likely because new Cypress versions use Will there be a new test for this in this repo? |
Yes, we are discussing this internally to ensure we have a test for the old headless mode. |
|
@mschile can you pin this issue? |
jennifer-shehane
added
stage: awaiting external fix
jennifer-shehane
changed the title
--headless=old in browser launch options--headless=old in browser launch options
|
Just clarifying the issue and who it’s affecting:
Root cause:
Available workarounds:
If you are encountering issues with any of these workarounds, please detail those issues and open an issue in GitHub. There are some users reporting hanging with the headless=new flag in Cypress, but we don’t have a way to reproduce that yet and would love to fix that. We don't expect Chrome to support the |
This comment was marked as resolved.
This comment was marked as resolved.
|
@MikeMcC399 Thanks, updated my comment to be clearer. |
|
Instead of See https://app.warp.dev/block/7kDNSkJQ4CtNDhMXPe3CRt in the original post. The error message may also be similar to: |
* Bumps cypress-io/github-action@v6 * Bumps cypress to v13.2.0 Related to cypress-io/cypress#27804
* Bumps cypress-io/github-action@v6 * Bumps cypress to v13.2.0 Related to cypress-io/cypress#27804
|
If using the |
|
You might find it simpler to use existing Cypress Docker images from name: Cypress Tests using Cypress Docker Image
on: push
jobs:
cypress-run:
runs-on: ubuntu-22.04
container:
image: cypress/browsers:node18.12.0-chrome106-ff106
options: --user 1001
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Cypress run
uses: cypress-io/github-action@v6
with:
build: npm run build
start: npm start
browser: chrome
|
|
@MikeMcC399 thanks, but as I mentioned in my post, we are not able to use custom images in our e2e CI because we are spinning up some containers before running the tests and containers under containers do not work it seems. |
|
According to https://storage.googleapis.com/chromium-find-releases-static/441.html#441de2f21f1d43a751b5f87f5240252654135a76 the fix is now in the pipeline for |
Because of errors in the communication between Cypress and Chrome 117+ we need to make sure that we run Chrome 116. This is a temporary solution and we should upgrade the cypress action in the future as a part of the work involved in upgrading Cypress. The GitHub issue that lead us to the problem: cypress-io/cypress#27804
* Bumps cypress-io/github-action@v6 * Bumps cypress to v13.2.0 Related to cypress-io/cypress#27804
|
I can confirm Google Chrome / Chromium Linux 117.0.5938.132 no longer has this issue On Windows/Mac it is slowly rolling out |
|
Closing as resolved. If you are experiencing a similar issue, please open a new issue describing the behavior and filling out our issue template. |
|
It will take a few days before the patched Chromium / Chrome / Edge
It needs a minimum Google Chrome Google Chrome Stable Channel Update for Desktop
Chromium 117.0.5938.132 release Log includes cea8ca44 [m117] Fix crash in HeadlessRequestContextManager. by Liza Burakova On Windows Microsoft Edge |
This comment was marked as resolved.
This comment was marked as resolved.
* Bumps cypress-io/github-action@v6 * Bumps cypress to v13.2.0 Related to cypress-io/cypress#27804
* Bumps cypress-io/github-action@v6 * Bumps cypress to v13.2.0 Related to cypress-io/cypress#27804
|
In the meantime Google Chrome The problem described in this issue, related to Google Chrome |
jennifer-shehane
removed
the
stage: awaiting external fix
…io/cypress#27804 Signed-off-by: SuZhou-Joe <suzhou@amazon.com>
and others
Latest update:
#27804 (comment)
Current behavior
Right now when running against latest Chrome which released 18 hours ago for linux and max and using
--headless=old(because we're getting browser freezes / unresponsiveness with new headless mode), you get ECONNRESET error code while cypress is trying to connect to headless chrome:https://app.warp.dev/block/7kDNSkJQ4CtNDhMXPe3CRt
With DEBUG=cypress:server:util:process_profiler:
https://app.warp.dev/block/c2Par9SHLXvmbpt2Edtj90
With DEBUG=cypress:*
https://app.warp.dev/block/cJRcQGlGK0MVSaCHRd0xy9
Of interest:
Desired behavior
Run tests :)
Test code to reproduce
We have this currently to use the old headless mode and removing it makes it work:
Cypress Version
12.17.3
Node version
16.16.0
Operating System
macOS 13.5.1 (22G90) and linux (debian)
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: