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

Cypress 1.4.1 or 2.1.0 crashes on Windows 10 #1607

Closed
trobbins1981 opened this issue Apr 17, 2018 · 3 comments
Closed

Cypress 1.4.1 or 2.1.0 crashes on Windows 10 #1607

trobbins1981 opened this issue Apr 17, 2018 · 3 comments

Comments

@trobbins1981
Copy link

trobbins1981 commented Apr 17, 2018

Current behavior:

I launch cypress and I see my lists of tests.
I click on a test (it can be any test).
A chrome window briefly opens then it closes again

Desired behavior:

I would like for Cypress to work as designed, and start running my tests.

Steps to reproduce:

This issue appears to be intermittent. It never happened while I was on Cypress 1.4.1. Then, after upgrading to 2.1.0, it didn't happen at first, but then started to a week or so later. I then downgraded to 1.4.1 and it continued to happen. The next day, it started working again, but now today (a week later), it's crashing again.

Versions

Cypres 1.4.1 or 2.1.0
WIndows 10
Chrome 65

@trobbins1981
Copy link
Author

I think I found a temporary solution for fixing it. Last time this this happened, it started working after I had put my computer to sleep then brang it right back. I figured it was a coincidence. Well, just now, I put my computer to sleep and brought it back, and it's working again.

@Saibamen
Copy link
Contributor

Please retest with latest Cypress. Also install lates windows updates and npm

@cypress-bot cypress-bot bot added the stage: awaiting response Potential fix was proposed; awaiting response label Feb 25, 2019
@jennifer-shehane
Copy link
Member

jennifer-shehane commented Mar 8, 2019

Please try unsetting the NODE_OPTIONS environment variable if you have this set - as this causes Cypress to crash. This is due to an Electron bug prior to version 2.0.3, where having NODE_OPTIONS set causes either a failure or arguments to be ignored. electron/electron#12695 (comment)

To see all environment variables currently set

MacOS / Linux

printenv

Windows

SET

To unset NODE_OPTIONS environment variable

MacOS / Linux

unset NODE_OPTIONS # this is not the same as export NODE_OPTIONS=

Windows

set NODE_OPTIONS=

We have open issues for this being fixed that you can follow here:

@jennifer-shehane jennifer-shehane removed the stage: awaiting response Potential fix was proposed; awaiting response label Mar 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants