Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove line item about Docker workaround and the open issue #5223

Merged
merged 1 commit into from
Apr 26, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions docs/guides/references/error-messages.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -939,11 +939,9 @@ This can happen for a number of reasons, including:

- The browser was exited manually, by clicking the "Quit" button or otherwise
- Your test suite or application under test is starving the browser of
resources, such as running an infinite loop
resources.
- Cypress is running in a memory-starved environment
- The browser is testing a memory-heavy application
- Cypress is running within Docker (there is an easy fix for this: see
[this thread](https://github.com/cypress-io/cypress/issues/350))
- There are problems with the GPU / GPU drivers
- There is a bug in the browser involving memory management
- There is a memory leak in Cypress
Expand All @@ -957,9 +955,6 @@ If you are running in `open` mode, you can also try lowering
If the browser running Cypress tests crashes, Cypress will abort any remaining
tests and print out this error.

There is an [open issue](https://github.com/cypress-io/cypress/issues/349) to
recover from browser crashes automatically, so tests can continue to run.

## Cypress App errors

### <Icon name="exclamation-triangle" color="red" /> Whoops, we can't run your tests
Expand Down