Cypress slows down and then crashes during cypress run

Hey there, I’m new to Cypress and things we going well, but now things are starting to crash now that I have a larger test suite. I’ve noticed that this sort of issue was filed a bunch of times before (https://github.com/cypress-io/cypress/issues/431) but I’m just not sure what I should be doing to fix the issue…

Current behavior:

Here’s an error report from Terminal when running with Electron 59. Things started to get pretty slow before it completely died.

<--- Last few GCs --->

[68129:0x7ff0b0854800]   198798 ms: Mark-sweep 2053.6 (2155.9) -> 2053.6 (2140.9) MB, 1574.1 / 78.1 ms  (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1574 ms) last resort
[68129:0x7ff0b0854800]   200480 ms: Mark-sweep 2053.6 (2140.9) -> 2053.6 (2140.9) MB, 1681.6 / 78.6 ms  last resort


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0xa0bb29f87e9 <Window map = 0x2039cbd43f99>
    2: getInitialState [http://localhost:3000/app.js:415928] [bytecode=0xabd9ae04d21 offset=1](this=0x2e5ba689d021 <ResizeStore map = 0xcd2a0fbe271>)
    4: constructor(aka Store) [http://localhost:3000/app.js:418152] [bytecode=0xb271520bc51 offset=39](this=0x2e5ba689d021 <ResizeStore map = 0xcd2a0fbe271>)
    6: new constructor(aka ResizeStore) [http://localhost:3000/app.js:41...

Those constructors are objects in my code. I don’t think there’s a memory leak in my application code. I have a few custom commands that access some objects off of the window but I’m navigating around which should garbage collect everything. Not sure what Cypress is doing internally… Maybe its keeping everything around?

Also, happy to try whatever you want to see if we can get this working 👍 I really like everything else about Cypress!

Versions

ProductName: Mac OS X ProductVersion: 10.14 BuildVersion: 18A391

Cypress: 3.1.5

[ccorcos]

It has been 5 months with no progress on this issue. I would not rely on Cypress fixing this issues. I’ve moved my company on to using the selenium-webdriver package. The only (small) hurdles were implementing my own retry-timeout and wrapping errors into better error messages.

For now, I’m going to close this issue because it is not making progress and is giving people a false sense of hope.

[ccorcos]

After adding the "numTestsKeptInMemory": 1 option, running from the GUI succeeds without crashing. 🎉