fix: Update Chrome renderer crash to be more terse and up to date

[jennifer-shehane]

Additional details

In Cypress, when the Chromium renderer crashes, we display a very long error message. Some of the error is not actionable, some of the recommendations are outdated, some of it is repetitive. Overall, the content of the message may be ignored or some of the solutions inapplicable by users.

We wanted to improve the error message to be terse and actionable, leading them to the docs for more detail cypress-io/cypress-documentation#5223.

Steps to test

Snapshots should test this - they need to be updated.

How has the user experience changed?

Before

After

What changed

• Removal of 'sad face' note - this seems irrelevant and not actionable - it's just taking up space to get to a solution.
• Removed list of arbitrary reasons this may happen (most of these were not actionable, so what's the point), we can list these in the docs if it's really necessary.
• Removed indication of issue with Docker - this was actually fixed in Cypress, this workaround is no longer necessary. See Docker crashes when renderer process eats up too much memory #350 (comment)
• Removed duplicate lists with numTestMemory and experimental flag - consolidated into one list for easier readability.
• Added recommendation to increases resources on the machine
• Indicated that numTestsKeptInMemory should be change in config during 'cypress open' (this config has no effect during cypress run)

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation? Remove line item about Docker workaround and the open issue  cypress-documentation#5223

[cypress]

25 flaky tests on run #45938 ↗︎

0

27269

1307

0

25

Details:

Merge branch 'develop' into chrome-renderer-crash-error-update
Project: cypress	Commit: aeb4067901
Status: Passed	Duration: 19:24 💡
Started: May 1, 2023 5:58 PM	Ended: May 1, 2023 6:17 PM

  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-firefox

View Output Video

Test		Artifacts
network stubbing > intercepting request > can delay and throttle a StaticResponse		Output

  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-electron

View Output Video

Test		Artifacts
network stubbing > intercepting request > can delay and throttle a StaticResponse		Output Video

  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-firefox

View Output Video

Test		Artifacts
... > correctly returns currentRetry		Output
... > correctly returns currentRetry		Output
... > correctly returns currentRetry		Output

  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron

View Output Video

Test		Artifacts
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video

  specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e

View Output Video

Test		Artifacts
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs		Output Screenshots Video

The first 5 flaky specs are shown, see all 14 specs in Cypress Cloud.

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[cypress-bot]

Released in 12.12.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.12.0, please open a new issue.