Cypress v3.3.0 hangs

[kweiberth]

Current behavior:

After upgrading to Cypress v3.3.0, I'm experiencing hanging tests, similar to the ones described in #1235 and #1333. The DEBUG=cypress:* logs continuously show the following logs once it hangs:

 cypress:server:timers child sending timer id 28 +6s
  cypress:server:timers child sending timer id 29 +277ms
  cypress:server:video capture stderr log { message: 'frame= 2793 fps= 27 q=13.0 size=    4608kB time=00:01:51.52 bitrate= 338.5kbits/s dup=2099 drop=0 speed=1.09x    ' } +552ms
  cypress:server:timers child sending timer id 30 +119ms
  cypress:server:timers child sending timer id 31 +298ms
  cypress:server:timers child sending timer id 32 +51ms
  cypress:server:video capture stderr log { message: 'frame= 2805 fps= 27 q=12.0 size=    4608kB time=00:01:52.00 bitrate= 337.0kbits/s dup=2103 drop=0 speed=1.09x    ' } +498ms
  cypress:server:video capture stderr log { message: 'frame= 2819 fps= 27 q=13.0 size=    4608kB time=00:01:52.56 bitrate= 335.4kbits/s dup=2108 drop=0 speed=1.09x    ' } +551ms
  cypress:server:timers child sending timer id 33 +1s
  cypress:server:timers child sending timer id 34 +86ms
  cypress:server:video capture stderr log { message: 'frame= 2833 fps= 27 q=12.0 size=    4608kB time=00:01:53.12 bitrate= 333.7kbits/s dup=2118 drop=0 speed=1.09x    ' } +593ms
  cypress:server:video capture stderr log { message: 'frame= 2846 fps= 27 q=12.0 size=    4864kB time=00:01:53.64 bitrate= 350.6kbits/s dup=2122 drop=0 speed=1.09x    ' } +510ms

Desired behavior:

Tests shouldn't hang and all tests should pass. Desired behavior is restored when I revert to Cypress v3.2.0

Steps to reproduce: (app code and test code)

Unfortunately I don't have a chance right now to try and set up a reproducible example. However, v3.3.0 consistently hangs, and v3.2.0 consistently passes.

Versions

Cypress: 3.3.0
Browser: Electron 61

[jennifer-shehane]

Hey @kweiberth, could you provide details about your CI server?

Also, if you could, please try to run the tests using cypress open and choosing the Electron browser with DevTools open - note any errors occurring here for us.

We will definitely need more information here as the information given is not helpful in isolating the problem unfortunately.

[noobling]

I had the same issue today. The whole cypress window hangs e.g. the timer stops. For me I fixed it by rearranging my test that caused cypress to hang and it seem to work fine...

[randing89]

Same here. If I run it locally the iframe that displays the UI in the middle is completely frozen.
The log is like this

  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +0ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.9121330451835215, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +1ms
  cypress:server:timers child sending timer id 35 +19s
  cypress:server:timers child sending timer id 37 +774ms
  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +0ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.27802936598884, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +1ms
  cypress:server:timers child sending timer id 51 +5s
  cypress:server:timers child sending timer id 53 +384ms
  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +0ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.2397979064758744, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +0ms
  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +1ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.23825683881274062, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +1ms
  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +0ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.49079102256314777, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +0ms
  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +0ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.7071413449160777, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +1ms

The UI won't stuck if I ran the test in Chrome. Here is the log:

  cypress:server:events got request for event: get:project:status, { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests' } +10s
  cypress:server:project get project status for undefined /Users/ran/src/confluence-frontend/next/packages/integration-tests +10s
  cypress:server:project no project id +0ms
  cypress:server:events sending ipc data { type: 'get:project:status', data: { id: 0.6056192172812374, data: { path: '/Users/ran/src/confluence-frontend/next/packages/integration-tests', state: 'VALID' } } } +1ms
  cypress:server:server Getting remote state: { auth: null, props: { port: '443', tld: 'net', domain: 'atlassian' }, origin: 'https://confluence-frontend-fabric-sev1-tests.atlassian.net', strategy: 'http', visiting: false, domainName: 'atlassian.net', fileServer: null } +3s

[kweiberth]

I see a bunch of these errors throughout my tests:

Error while parsing the 'allow' attribute: 'accelerometer;', 'autoplay;', 'encrypted-media;', 'gyroscope;', 'picture-in-picture' are invalid feature names.

Interestingly, like @randing89 mentions, this has to do with an iframe, specifically a YouTube iframe.

My test suite suite consistently hangs at the start of the fourth describe() block. If I skip the first describe() block, which has these errors, everything runs smoothly. I can also run .only() the fourth describe block, and everything runs smoothly.

Also, during this first describe block, the Cypress UI "hangs" in that the tests pass and the test runner moves on, but the UI would suggest it's still stuck on the first test:

All of this is happening with Electron 61. Everything runs smoothly with Chrome 74.

Last, this is happening not only on CI like my original post suggested, but locally too. I've updated my original post to remove references to my CI server.

[jennifer-shehane]

@kweiberth I am able to reproduce this console.error

index.html

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Cypress.io YouTube</title>
</head>
<body>
<iframe width="560" height="315" src="https://www.youtube.com/embed/dr10Z-HpsCQ" frameborder="0"
  allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</body>
</html

test.js

describe('youtube', () => {
  beforeEach(() => {
    cy.visit('index.html')
  })

  it('test', () => {
    expect(true).to.eq(true)
  })
})

Open the DevTools console to see the console errors:

On initial thought, I thought it had something to do with Chrome's Autoplay policy changes that maybe some of it took effect in Chromium 61, but I don't know why these errors would then disappear when running the tests in Chrome 74. Plus it doesn't look like much of this was implemented for Chromium 61.

Am going to do some more research.

[jennifer-shehane]

Also, I'm not sure if the issue @kweiberth described is the same 'hanging' issue everyone else is having. Can anyone confirm if they are using video embedded in iframes? If not, we should probably move these autoplay problems to a new issue.

[beepboopitschloe]

My tests are also hanging in CI, but I'm not using video or iframes.

[immunity20]

Same problem here.
with Electron 61.
I have 5 integrations tests (1st, 2nd and 3rd are similar)
3rd test hang waiting for xhr response (although the server shows the 200

that xhr request is requested (with slightly different variables) multiple times in all tests.
but for some reason Electron 61 (headless or window) hangs always in the same particular request xhr (which it already has sent ~8 more in the same test) . If i try to run the test (while Electron 61 is hanging) with chrome, the Electron 61 start to respond again (When chrome browser does the same request)

[huyvanvu]

Same problem. Failed at Electron 61 but work well with Chrome. I don't have either video embedded or iframes. After trying these steps, it's now working for me.

1. Delete folder Cypress in C:\Users\***\AppData\Roaming. Where *** is your username.
2. Delete node_modules
3. Run yarn

[jennifer-shehane]

We'll need something we can run to reproduce the hanging issue. Can't debug this without that.

[rafael-anachoreta]

My case has been the opposite - Chrome will sometimes hang whereas Electron never seems to. I've had this happen on 3.1.0, 3.2.0 and 3.3.1.

I don't have a reproducible example I can share at the moment other than my DEBUG logs, which I would rather share privately. @jennifer-shehane if you think those could help let me know and please advise how I could share them.