UI crashing on Mac OS

[mukaibot]

Current behavior

Cypress is quitting unexpectantly when I open the UI and click the "Start E2E testing in Chrome" button. This prevents me from running my E2E tests. (Apologies for the grainy video, there is a 10MB attachment limit on the ticket)

Cypress executes correctly when run from the command line eg cypress run

cypress_crash.mov

debug.log

Desired behavior

I should be able to execute my tests from npx cypress open

Test code to reproduce

I'm not sure how to give you reproducible code. Beyond debug logs, please advise!

Cypress Version

13.8.1

Node version

v18.17.1

Operating System

MacOS 14.4.1

Debug Logs

See attachment

Other

No response

[jennifer-shehane]

Is this your first time using Cypress and it has never worked? Or did it previously open and now it’s not? If used previously, did anything change between that run and this run?

[mukaibot]

thanks for the reply. Older versions have worked previously, but haven't run Cypress for a few months. There have been updates to Mac OS and Cypress since then. I appreciate this is a tough one to troubleshoot. I had searched for the error TypeError: Parser can work only with string streams. in the issues here but didn't find anything.

I have tried downgrading to older versions in Cypress 12 and 13, but I am getting the same TypeError, which leads me to believe there may be an issue with Node or one of the packages Cypress is using on Mac.

I guess this may stay open until someone else reports they are having the same issue?

[mukaibot]

I tried this in a Windows 11 VM and am getting the same error: Parser can work only with string streams, so it seems that the issue is not just Mac.

Additionally two other developers on my team are also experiencing the same issue.

What additional information can I provide here?

[mukaibot]

I think I have figured this out. The line in our configuration experimentalModifyObstructiveThirdPartyCode: true is causing the issue. Deleting this line seems to allow Cypress to work now!