question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cypress performance degrades to the point of failure in Chrome 79 on Ubuntu

See original GitHub issue

Current behavior:

I can run my tests fine using Cypress 3.4.1 or 3.8.0 against Chrome 78 on Ubuntu 18.04, but if I update to Chrome 79, Cypress starts hanging in random places in my test (as in, the tests hang 0-20 seconds in, but at a different point each time I try). All the Cypress controls (e.g. Stop button) become unresponsive and I can only close the Chrome window.

Desired behavior:

I want to be able to use Cypress against the latest Chrome version.

Steps to reproduce: (app code and test code)

I’ve reproduced this using the following basic test:

describe('page', () => {
  for (let i=1; i <= 30; i++) {
    it(`test ${i}`, () => {
      cy.visit('https://www.google.com');
    });
  }
});

It’s usually hanging indefinitely after about 12-15 tests when using cypress open. Note that it’s very choppy even when the tests are still running, with multiple seconds between updates to the elapsed time and the rest of the window.

Interestingly, cypress run --browser "chrome" does better. It’s still choppy, but it eventually finishes even if I bump i up to 100.

If I uninstall Chrome 79 and install Chrome 78 from an archive, the tests run to completion and the window remains responsive for the whole run.

Versions

Cypress 3.4.1 - 3.8.0 (at least–I didn’t try anything older) Chrome Version 79.0.3945.88 (Official Build) (64-bit) Ubuntu 18.04.3 LTS

This is not seen in Chrome 79 on Mac or Windows

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:7
  • Comments:19 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
clarmsocommented, Jan 10, 2020

Looks like the performance is specific to Chrome 79, not Cypress. 😦 https://support.google.com/chrome/thread/24842699?hl=en

2reactions
clarmsocommented, Jan 6, 2020

@jennifer-shehane I got some performance issues on Chrome 79+ with Cypress 3.6.1 and 3.8.1 on Ubuntu, too. Setting DEBUG=cypress:* on the CLI generates tons of logs. Are there any particular items on the log that may indicate performance issues in this case?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting | Cypress Documentation
Troubleshooting · Support channels · Isolate the Problem · Download specific Chrome version · Clear Cypress cache · Launching browsers · Allow the...
Read more >
How can I run my tests with older chrome version in cypress
Now my cypress version is 3.8.2 And when I am opening cypress window there are chrome version is 79. I want to run...
Read more >
Downloads - ChromeDriver - WebDriver for Chrome
ChromeDriver 79.0.3945.16. Supports Chrome version 79. Fixed ChromeDriver crash caused by javascript alert fired during command execution; Fixed a ...
Read more >
Quickly Export Cypress Tests Directly from Google Chrome
Join the Cypress Tools Team, along with Jecelyn Yeen from Google DevTools, to learn more about Chrome's new DevTools Recorder and Cypress ' ......
Read more >
Google Chrome - Download the Fast, Secure Browser from ...
Laptop and mobile device, displaying the Google.com home page. Built for performance. The faster browser. Chrome is faster than fast – it's engineered ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found