cypress: We detected that the Chromium Renderer process just crashed Cypress CI error

Current behavior

I get this error when I run my Cypress test scripts on Azure CI server.

<--- Last few GCs --->

[8736:0x2f6c003b0000]   987167 ms: Scavenge 397.7 (437.8) -> 391.8 (438.0) MB, 6.0 / 0.0 ms  (average mu = 0.998, current mu = 0.998) allocation failure; 
[8736:0x2f6c003b0000]   988392 ms: Scavenge 397.9 (438.0) -> 392.6 (438.8) MB, 8.7 / 0.0 ms  (average mu = 0.998, current mu = 0.998) allocation failure; 
[8736:0x2f6c003b0000]   988595 ms: Scavenge 399.3 (438.8) -> 392.6 (439.8) MB, 10.2 / 0.0 ms  (average mu = 0.998, current mu = 0.998) allocation failure; 


<--- JS stacktrace --->

[8736:1124/101216.876419:ERROR:v8_initializer.cc(730)] V8 process OOM (Oilpan: Reserving memory.).

We detected that the Chromium Renderer process just crashed.

This is the equivalent to seeing the 'sad face' when Chrome dies.

This can happen for a number of different reasons:

- You wrote an endless loop and you must fix your own code
- You are running Docker (there is an easy fix for this: see link below)
- You are running lots of tests on a memory intense application
- You are running in a memory starved VM environment
- There are problems with your GPU / GPU drivers
- There are browser bugs in Chromium

I tried adding the option –browser chrome to the cypress run command, but it makes the tests fail many assertions (assertions that would not fail if I run without the browser chrome option) unexpectedly.

PS. the same test scripts would run fine in cypress 10.7.0, electron 102. But now, they fail with the mentioned error in cypress 11.2.0, electron 106. I think the failure is more related to electron browser version, but I am not certain.

Desired behavior

No response

Test code to reproduce

npx cypress run

Cypress Version

11.2.0

Node version

12.22.9

Operating System

Ubuntu 22.04.1 LTS

Debug Logs

No response

Other

No response

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 2
Comments: 21 (4 by maintainers)

Most upvoted comments

Hi, I am using the latest version of Cypress which is 12.14.0 and I also have experimentalMemoryManagement: true, but still it’s crashed.

We detected that the Chromium Renderer process just crashed.

This can happen for a number of different reasons.

If you're running lots of tests on a memory intense application.
  - Try increasing the CPU/memory on the machine you're running on.
  - Try enabling experimentalMemoryManagement in your config file.
  - Try lowering numTestsKeptInMemory in your config file during 'cypress open'.

I am now also planning to try with numTestsKeptInMemory: 20,

rakeshnambiar on Jun 18, 2023

@AnushaAshokReddy, the latest version of Cypress doesn’t have the text that is displayed in your screenshot. Is the screenshot from a different version?

mschile on Jul 18, 2023

We are releasing in 12.4.0 next week an option called experimentalMemoryManagement, which should help cut down on this issue. Would any of you be willing to try this in CI and see if the issue improves?

For me, the new experimentalMemoryManagement works fine. Our OOM-Errors are gone 😃

ClaasWilke on Jan 26, 2023

am using the cypress version 12.7.4; Browser - Electron 106(headless); Node version v16.20.1 and the same below in m projectory and still am getting this issue. Can anyone help me here please

numTestsKeptInMemory: 0, experimentalMemoryManagement: true,

Below is the error :

We detected that the Chromium Renderer process just crashed. This can happen for a number of different reasons. If you’re running lots of tests on a memory intense application.

Try increasing the CPU/memory on the machine you’re running on.
Try enabling experimentalMemoryManagement in your config file.
Try lowering numTestsKeptInMemory in your config file during ‘cypress open’.

dummulokesh2105 on Jan 11, 2024

@AnushaAshokReddy, it looks like you’re using an older version of Cypress which does not support experimentalMemoryManagement. Please see this comment for required Cypress versions.

mschile on Jul 18, 2023

I still have this issue happening in jenkins. We are running only 10 tests in parallel with 5 containers and 2 of them fail with the chrome renderer issue. Tried the ‘experimentalMemoryManagement’ flag ‘true’ - this also did not solve the issue.

Here is the screenshot :

AnushaAshokReddy on Jul 18, 2023

@AtofStryker we’ll try it for sure

Jacek-fstack on Jan 24, 2023

We also are getting We detected that the Chromium Renderer process just crashed almost every time with Cypress 11.2.0. Though everything was ok with Cypress 9.6.0.

We are using cypress circleci-orb (version 2.2.0) and cypress/browsers:node16.16.0-chrome107-ff107 executor.

alesiaviktorchyk on Dec 20, 2022