That's frustrating. It does make me think "memory leak". Do you have any colleagues who see the same error when they run this test? If others can run it, perhaps you can improve the situation with

npm install

or

npm update

. Also, if you are doing anything unconventional in your tests (writing to console with every step) maybe try eliminating that stuff to see if it changes anything. You might also tinker with the soon-to-be-deprecated

nodeVersion

config option. https://docs.cypress.io/guides/references/configuration#Node-version