Cypress test runner crashed/getting Aw,snap error in vs code even if i added "numTestsKeptInMemory": 0, in cypress.json file

[vijay-peruri53]

Current behavior

Cypress test runner crashed/getting Aw,snap error in vs code even if i added "numTestsKeptInMemory": 0, in cypress.json file

Desired behavior

No response

Test code to reproduce

if i execute the scripts for sometime i am getting this Aw, snap errror and failing

Cypress Version

5.6.0

Other

No response

[kolorfilm]

same problem here

[rockindahizzy]

Hey @vijay-peruri53 thanks for submitting the issue!

• Are you able to upgrade to a newer version of Cypress? It's possible that the issue you are experiencing has been resolved in a more recent version of Cypess.
• Is it possible for you to provide a reproduction of this issue?

@kolorfilm, are you experiencing this issue on 5.6.0 or a different version of Cypress?

[kolorfilm]

@kolorfilm, are you experiencing this issue on 5.6.0 or a different version of Cypress?

On the latest version of Cypress

[vijay-peruri53]

@rockindahizzy I am facing the issue in 5.6.0 version previously i am not facing this issue but since few days i am seeing this issue.

[Georgi0304]

I am facing the issue last few days with the latest version of cypress. My test was running fine for 23 mins last week and this week it crashes at about 8 mins.

[yellowee]

It keeps crashing for me too - Cypress 10, I use webstorm

[rockindahizzy]

Hey @vijay-peruri53, are you able to upgrade to a more recent version of Cypress? You may see performance improvements.

[vijay-peruri53]

@rockindahizzy I will try to upgrade to recent version. can You let me what are the changes from version 5.6.0 to 10.4.0..!

and can you guide me what are the framework level changes i have to do.

[rockindahizzy]

@vijay-peruri53, there have been quite a few changes during that timespan. You can find all of the changes in this change log.

In the Major version markers of the change log (for example 10.0.0), we highlight breaking changes. Also, you will find a migration guide to help migrate to a new version. You may need to look through the migration guides starting at v6.0.0 and decide the best approach for your specific project.

[vijay-peruri53]

@mike-plummer and @rockindahizzy in the above comments i see that for the latest version of cypress also having this issue. is there any complete solution for this issue.

[mike-plummer]

@vijay-peruri53 Unfortunately we do not have enough information to reproduce this issue on our end. We would need more information about the environment where you're trying to run Cypress (OS version, Node version, memory allocations, etc) and a test suite that reliably reproduces the issue. Without a reproducible example we can't start narrowing down whether it's an issue with Cypress itself, a memory leak in your tests, an out of date browser, or another issue entirely. Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide.

While a reproducible example is best, at a minimum we would ask if you could run Cypress in debug mode mode and attach the log output here. It would be best to update to the latest version of Cypress before doing so just to eliminate any potential variables.

[tpodolskiy]

same with 10.6 its awkward, consistently after running 5 -6 tests

[nagash77]

Unfortunately we have to close this issue due to inactivity. If anyone following along with this ticket can provide us with a reproducible example/repo please do comment and we can reopen.

[samelawrence]

I still experience this issue in Cypress 12+. I have never been able to use the replay feature of Cypress because of this. It happens across multiple machines I run Cypress on. It has never worked for me (MacOS, latest version, 16GB of RAM+, etc.)

[nagash77]

@samelawrence please open a new issue with a reproducible example and the Cypress team will be happy to investigate.