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

Process Crash During Cypress Test Execution #30807

Closed
Tomoppenheimer opened this issue Dec 29, 2024 · 1 comment
Closed

Process Crash During Cypress Test Execution #30807

Tomoppenheimer opened this issue Dec 29, 2024 · 1 comment
Labels
type: duplicate This issue or pull request already exists

Comments

@Tomoppenheimer
Copy link

Test code to reproduce

The Chrome Renderer process crashes with the error message "Aw, Snap! Something went wrong while displaying this webpage," along with an error code of STATUS_BREAKPOINT. Attached are screenshots of the issue for your reference:

image
image

From the logs, I noticed the following suggestions:
Increase CPU/memory resources on the machine.
Enable experimentalMemoryManagement in the Cypress configuration file.
Lower the numTestsKeptInMemory value during cypress open.

Despite attempting some of these solutions, the issue persists intermittently, particularly during some specific tests.
Here is some additional context about my setup:
Cypress version: 13.16.1 (issue occurs also in version 13.17.0)
Browser: [Chrome version131]
Machine specs: 12th Gen Intel(R) Core(TM) i7-1260P 2.10 GHz, 40.0 GB RAM (Issue also occurs in MacBooks)

image

image

Cypress Mode

cypress open

Cypress Version

13.16.1 and 13.17.0

Browser Version

131.0.6778.205 (Official Build) (64-bit)

Node version

v20.10.0

Operating System

Windows 10 and 11, and macOS ersion 15.2 (24C101)

Memory Debug Logs

No response

Other

It happens also in Headless mode.

@jennifer-shehane
Copy link
Member

@Tomoppenheimer Could you provide a reproducible example? If so, please add it to this issue, which this is a duplicate of #27415

These are hard to track down honestly because it could be a number of causes including the application under test having a memory leak itself.

@jennifer-shehane jennifer-shehane closed this as not planned Won't fix, can't repro, duplicate, stale Dec 30, 2024
@jennifer-shehane jennifer-shehane added the type: duplicate This issue or pull request already exists label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants