This repository was archived by the owner on Jul 2, 2024. It is now read-only.
EVG-18656 Fix OOM when running long running cypress tests locally #159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EVG-18656
Description
There appears to be some sort of problem with the more recent versions of cypress and chrome. Long-running tests are OOMing and crashing when run locally. Taking a look at the memory usage of the cypress process the longer the test runs the more memory it uses until it crashes. Luckily there's a flag we can toggle to help out with this but we should keep an eye on the issue for future cypress releases.
cypress-io/cypress#21135
cypress-io/cypress#23391
cypress-io/cypress#24905
Also updates cypress for good measure https://docs.cypress.io/guides/references/changelog#12-3-0
Screenshots
Cypress Memory usage

Before:
https://user-images.githubusercontent.com/4605522/210657670-3a45a3a3-6bee-4641-ab74-23d97a1d449e.mov
After:
Testing
Run cypress tests locally in chrome should no longer OOM (resmoke_filtering in particular)