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

“Aw, Snap!” Out of memory issue in Chrome under Cypress #30923

Open
ManeeshaS294 opened this issue Jan 22, 2025 · 1 comment
Open

“Aw, Snap!” Out of memory issue in Chrome under Cypress #30923

ManeeshaS294 opened this issue Jan 22, 2025 · 1 comment
Labels
stage: needs information Not enough info to reproduce the issue type: performance 🏃‍♀️ Performance related

Comments

@ManeeshaS294
Copy link

ManeeshaS294 commented Jan 22, 2025

Test code to reproduce

we have 41 test cases in our feature file, so far when we execute them together browser crash and give us "Aw Snap Out Of Memory"
error. Can you please help us to resolve that issue.

Configuration File

//cypress.config.ts

import { defineConfig } from 'cypress'

export default defineConfig({
  video: false,
  numTestsKeptInMemory: 1,
  screenshotOnRunFailure: true,
  trashAssetsBeforeRuns: true,
  experimentalMemoryManagement: true,
  experimentalInteractiveRunEvents: true,
  watchForFileChanges: true,
  env: {
    CYPRESS_NO_COMMAND_LOG:1,
    wait: {
      maxWait: 5000000,
      mediumWait: 50000,
      minWait: 50000
    }
  },
  e2e: {
    specPattern: 'cypress/e2e/**/*.feature',
    supportFile: 'cypress/support/e2e.ts',
    testIsolation: true,
    experimentalMemoryManagement: true,
    numTestsKeptInMemory: 0,
    setupNodeEvents
  }
});

Issue Screenshot

Image

Cypress Mode

cypress run

Cypress Version

14.0.0

Browser Version

Chrome 132.0.6834.84

Node version

22.13.0

Operating System

Windows10

Memory Debug Logs

Other

No response

@jennifer-shehane
Copy link
Member

@ManeeshaS294 Is this a new issue? Is so, did something change between the tests running and failing?

Memory crashing the browser can have several causes, including a memory leak within the application under test itself, so it's impossible for us to assess the cause without a reproducible example.

Without any knowledge of your test suite, the first thing I'd suggest is reducing the size of a single test.

@jennifer-shehane jennifer-shehane added stage: needs information Not enough info to reproduce the issue type: performance 🏃‍♀️ Performance related labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage: needs information Not enough info to reproduce the issue type: performance 🏃‍♀️ Performance related
Projects
None yet
Development

No branches or pull requests

2 participants