cypress: Cypress crashes with "We detected that the Chromium Renderer process just crashed."

Test code to reproduce

I cannot provide the specific test code I am using to produce this, since it contains internal company data. However, what I can tell you is these tests run for quite a long time (5-10 minutes), as they contain a lot of steps through our E2E flow in our application.

Cypress Mode

cypress run

Cypress Version

12.13.0

Browser Version

Chrome 110.0.5481.96

Node version

v16.18.1

Operating System

Debian GNU/Linux 11 (Docker image cypress/browsers:node-16.18.1-chrome-110.0.5481.96-1-ff-109.0-edge-110.0.1587.41-1)

Memory Debug Logs

Only the end of the failing test results from the memory dump have been included due to limitations of this input form.

[
  {
    "checkMemoryPressureDuration": 7764.029118001461,
    "testTitle": "Crashing test (example #1)",
    "testOrder": 18.2,
    "garbageCollected": true,
    "timestamp": 1690553650738
  },
  ...
  {
    "getRendererMemoryUsageDuration": 2.619260013103485,
    "totalMemoryWorkingSetUsed": 6995816448,
    "getAvailableMemoryDuration": 58.69076597690582,
    "jsHeapSizeLimit": 4294705152,
    "totalMemoryLimit": 9223372036854772000,
    "rendererProcessMemRss": 5469155328,
    "rendererUsagePercentage": 127.34646813770371,
    "rendererMemoryThreshold": 2147352576,
    "currentAvailableMemory": 9223372029858955000,
    "maxAvailableRendererMemory": 4294705152,
    "shouldCollectGarbage": true,
    "timestamp": 1690553801030,
    "calculateMemoryStatsDuration": 58.72436600923538
  },
  {
    "getRendererMemoryUsageDuration": 2.208419978618622,
    "totalMemoryWorkingSetUsed": 5089853440,
    "getAvailableMemoryDuration": 61.31387501955032,
    "jsHeapSizeLimit": 4294705152,
    "totalMemoryLimit": 9223372036854772000,
    "rendererProcessMemRss": 0,
    "rendererUsagePercentage": 0,
    "rendererMemoryThreshold": 2147352576,
    "currentAvailableMemory": 9223372031764918000,
    "maxAvailableRendererMemory": 4294705152,
    "shouldCollectGarbage": false,
    "timestamp": 1690553802092,
    "calculateMemoryStatsDuration": 61.33369600772858
  },
  {
    "getRendererMemoryUsageDuration": 2.69021999835968,
    "totalMemoryWorkingSetUsed": 1682976768,
    "getAvailableMemoryDuration": 50.05962598323822,
    "jsHeapSizeLimit": 4294705152,
    "totalMemoryLimit": 9223372036854772000,
    "rendererProcessMemRss": 0,
    "rendererUsagePercentage": 0,
    "rendererMemoryThreshold": 2147352576,
    "currentAvailableMemory": 9223372035171795000,
    "maxAvailableRendererMemory": 4294705152,
    "shouldCollectGarbage": false,
    "timestamp": 1690553803143,
    "calculateMemoryStatsDuration": 50.07922601699829
  },
  {
    "getRendererMemoryUsageDuration": 2.889739990234375,
    "totalMemoryWorkingSetUsed": 1682792448,
    "getAvailableMemoryDuration": 60.31445497274399,
    "jsHeapSizeLimit": 4294705152,
    "totalMemoryLimit": 9223372036854772000,
    "rendererProcessMemRss": 0,
    "rendererUsagePercentage": 0,
    "rendererMemoryThreshold": 2147352576,
    "currentAvailableMemory": 9223372035171979000,
    "maxAvailableRendererMemory": 4294705152,
    "shouldCollectGarbage": false,
    "timestamp": 1690553804204,
    "calculateMemoryStatsDuration": 60.33361500501633
  },
  {
    "getRendererMemoryUsageDuration": 2.6974300146102905,
    "totalMemoryWorkingSetUsed": 1682558976,
    "getAvailableMemoryDuration": 225.94400304555893,
    "jsHeapSizeLimit": 4294705152,
    "totalMemoryLimit": 9223372036854772000,
    "rendererProcessMemRss": 0,
    "rendererUsagePercentage": 0,
    "rendererMemoryThreshold": 2147352576,
    "currentAvailableMemory": 9223372035172213000,
    "maxAvailableRendererMemory": 4294705152,
    "shouldCollectGarbage": false,
    "timestamp": 1690553805431,
    "calculateMemoryStatsDuration": 225.9711429476738
  }
]

Other

Our test specs that contain multiple long running tests are prone to crashing mid-run in CI. This seems to be more likely when there are test retries in the run. We are running with both experimentalMemoryManagement set to true and numTestsKeptInMemory set to 0. We also have the memory and CPU allocation in our GitLab runners set quite high (see below). Despite this, we still get the crashes. Example:

Some top level test description
    (Attempt 1 of 4) A test scenario containing a scenario outline template (example #1)
    (Attempt 2 of 4) A test scenario containing a scenario outline template (example #1)
    ✓ A test scenario containing a scenario outline template (example #1) (849857ms)
    ✓ A test scenario containing a scenario outline template (example #2) (360954ms)
    ✓ A test scenario containing a scenario outline template (example #3) (556574ms)
    (Attempt 1 of 4) A test scenario containing a scenario outline template (example #4)

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'.

You can learn more here:

https://on.cypress.io/renderer-process-crashed

Here are the memory allocations we are providing in Gitlab CI:

  KUBERNETES_CPU_REQUEST: "3"
  KUBERNETES_CPU_LIMIT: "4"
  KUBERNETES_MEMORY_REQUEST: "12Gi"
  KUBERNETES_MEMORY_LIMIT: "32Gi"

It should be noted these tests run within docker in CI, and are running in the cypress/browsers:node-16.18.1-chrome-110.0.5481.96-1-ff-109.0-edge-110.0.1587.41-1 version of the cypress image.

We are utilizing the cypress-cucumber-preprocessor library, but I do not believe that is having any impact on this issue.

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 41
  • Comments: 138 (25 by maintainers)

Commits related to this issue

Most upvoted comments

@jennifer-shehane Hi! This has become a major blocker for my team in the past few months. We’re all running M2 MBPs with 32 GB of RAM, and are unable to test locally in any efficient manner because of these memory issues. Like others have stated, we’ve enabled experimentalMemoryManagement and reduced the numTestsKeptInMemory to 0 with no luck.

I understand that there may be multiple factors at play here, but this thread dates back to last year, with suggestions to use chrome versions almost 20 iterations old or non standard browsers. This can waste anywhere from 1-2 hours per developer per day, which quickly scales up to thousands of hours per year lost across the org alone. In an era where >50% web traffic comes through chromium browsers, using non-chromium browsers as a workaround is not a real solution. Other than your diligence in this thread which is greatly appreciated, what actions has the cypress team taken to resolve this issue?

@jennifer-shehane

I have produced an example that reliably reproduces this issue: https://github.com/Lasidar/cypress-memory-crash-repro.

Now, to answer your specific suggestions…

Try updating to latest Cypress version 13.6.6, we make improvements to performance nearly every release.

Updated to the latest but still seeing the crash.

Try updating your Chrome browser that you run on. Chrome may have made improvements to their memory management.

We are using the latest version of Chrome available, 122.

Try turning on experimentalMemoryManagement

Already on.

Try turning off Test Replay to see if it improves (Please open a new issue providing us with links to the Cloud run with and without Test Replay on if this is the case - we’ll investigate).

The issue seems to mostly happen when test replay is off, since I believe test replaying hiding the sidebar reduces the memory footprint of the renderer process.

Turn off video if you have it recording

We tried both with and without. The crash still happens in either case.

Split up your spec files into shorter duration Split your specs into shorter duration tests. experimentalMemoryManagement only clears memory between each test or retry, so if it’s a very long test - memory is never being cleaned up (this is unfortunately how Chrome works and is why we offered this workaround).

Practically speaking, this is not always an option. Some of our E2E tests have an indivisible flow which is large by the nature of what is being tested. Plus I do not accept this as a solution. We need to root cause the crash instead of pushing it back on the test developers to workaround this issue. I hope the example I have provided will allow the Cypress team to get more insight into the cause.

We’re looking into the ResizeObserver theory and reproduction. There’s a lot of deep diving into code involved, so we’ll update here once we have factual takeaways.

Hi @jennifer-shehane. I have some more data to share with you.

Since it was suggested that this is an issue with the plugin cypress-cucumber-preprocessor, of which we were using version 4.3.1, we updated to the latest maintained version @badeball/cypress-cucumber-preprocessor@20.0.2, but the issue was still observed. Additional logs have been provided under /logs_after_plugin_update in https://github.com/Lasidar/cypress-memory-crash-repro.

As a comparison point, we also created a new version of this example without Cucumber under YahooItemsFailNoCucumber.ts. This example also crashed. It should be noted this was with the plugin still installed but not used. Results for this run are found in CrashingRun_NoCucumber_WithVideo_Chrome.txt.

As a final comparison, we uninstalled the Cucumber plugin completely and re-ran YahooItemsFailNoCucumber.ts. The memory crash still occurred. Results can be found in CrashingRun_NoCucumberUninstalled_WithVideo_Chrome.txt. In order to run this example, you can check out the branch called cucumber-uninstalled, and execute npx cypress run --e2e --browser chrome -c video=true --spec cypress/tests/YahooItemsFailNoCucumber.ts.

I hope this additional detail helps us get closer to a solution, as neither upgrading the cucumber plugin or removing it entirely seems to have resolved the issue.

We´re at the 13.17.0 and this problem has been with us for many months. Can we expect some investigation and fix @jennifer-shehane ?

This issue is ongoing, so we´re already thinking about switching from Cypress to another solution.

Thank you

When will cypress fix this issue ?? or give us a work around that doesnt involve downgrading away from “cypress 13”. I am a big fan of Test replay.

It seems as if Chrome has been overwhelmed with the layout of our application including Cypress since version 115. Our application runs unstably when command-log window is displayed. As soon as an action is performed in the application that writes a new entry in the command log, the browser crashes. This is usually not easy to reproduce, but we were able to reproduce it in a test at some point. Debugging the Chrome crashdumbs didn’t help us either. Everything was stable up to version 114 of Chrome. Our solution is to set CYPRESS_NO_COMMAND_LOG: 1 now. Maybe it will help someone. We hope that at some point the problem will solve itself with a Chrome update or with a simpler cypress layout. Unfortunately, this is not that easy to reproduce in a small sample application.

@jennifer-shehane does the cypress team have any other insights as to what the cause might be? If we’ve ruled out cucumber, video capture doesn’t seem to be the cuprit, we have experimentalMemoryManagement on, and have updated everything to the latest versions, what does that leave? Is it possible there is a memory leak in the cypress process(es) themselves?

@nagash77 I understand that actually finding the root cause here will be extremely difficult. One thing I did find interesting when I was analyzing the memory usage leading up to the crash is between tests, the memory usage never returns back down to a baseline level. It is continually increasing. This is even with experimentalMemoryManagement set to true and numTestsKeptInMemory set to 0. I find this strange since I am not sure what would be persisting in memory between tests.

image

If a true root cause fix is not possible, I have a few possible suggestions:

  • Give the users control over the browser heap size allocation via a parameter in cypress.config.js. That way, instead of setting it through a before:browser:launch trigger, it could be set more transparently via a test configuration option.
  • In the event of a renderer crash, perhaps we could print more verbose memory statistics (i.e. max rendererProcessMemRss used, jsHeapSizeLimit, etc).
  • If possible, try and solve the K8s / docker issue (i.e. https://github.com/Zenika/alpine-chrome/issues/109), which I believe may be contributing to this issue.

Hello Cypress team, @jennifer-shehane! Is there any updates of this issue? This is a terrible problem for our tests runs, it crash with simple test steps, which means that we don’t know results of some of them. In our case it occurs in tests where Resize Observer loop error was ignored. Most of our test projects fail… Both locally and on CI. Cypress sugesstions with setting experimentalMemoryManagement and numTestsKeptInMemory does not helped. We noticed problem started after migration from ng14 to ng16.

I have a speculation as to what is causing this which is based on a few logical leaps, but I think they are reasonable. I think the issue is mainly caused by the open issues involving cypress and K8s (see https://github.com/Zenika/alpine-chrome/issues/109).

Looking at the logs in question, I noticed the jsHeapSizeLimit limit is being exceeded right before the crash.

    "jsHeapSizeLimit": 4294705152,
    "rendererProcessMemRss": 5469155328,
    "rendererUsagePercentage": 127.34646813770371,

This is strange, since we have 12GB allocated to the Gitlab runner, with the ability to scale up to 32GB if the process calls for it. But looking at the issue linked above, I believe this prevents the Chrome renderer from being able to scale up its heap memory usage, even if the system has capacity.

From looking at the Cypress source code, it seems the renderer process memory is pulled from the chrome jsHeap, and if we exceed this, we are likely smashing the stack which probably leads to the crash.

  // the max available memory is the minimum of the js heap size limit and
  // the current available memory plus the renderer process memory usage
  const maxAvailableRendererMemory = Math.min(jsHeapSizeLimit, currentAvailableMemory + rendererProcessMemRss)

So my workaround, at least temporarily, is to increase the chrome jsHeapSizeLimit value. I was able to achieve this through the following additions to my cypress/plugins/index.js file:

module.exports = (on, config) => {
  on("before:browser:launch", (browser = {}, launchOptions) => {
    if (browser.family === "chromium") {
      launchOptions.args.push('--js-flags="--max_old_space_size=1024 --max_semi_space_size=1024"');
    }
    return launchOptions;
  });
});

This seems to have made my memory crashing issues go away for the time being. I believe the correct fix for this is for https://github.com/Zenika/alpine-chrome/issues/109 to be resolved, since as I mentioned above, I suspect this issue prevents the process from being able to properly scale up its heap size.

We noticed that problem is on frontend side, more precisely in infinite resize loop, where ResizeObserver is fasten. When it “tells” us that it is resize, we change something in the UI before the view has time to be drawn (before paint), which causes resize again and so on. We added debounce for 10ms which breaks this loop because it creates UI modifications after drawing ( after paint) and it helped. Cypress probably somehow interferes with drawing views and intensifies an already existing problem in applications using ResizeObserver.

I’ve tried to resolve the problem from Cypress error handlers side, but Chrome crashes as long as there is an event listener attached to window.onerror even if it suppresses the event. Only the “absence” of error handlers improves the situation.

So I’ve addressed the problem from the root cause and resolved the “ResizeObserver loop” problem. Not by fixing my code, frankly I am not in control of all usages of this API, but from the ResizeObserver side.

The following snippet replaces the default implementation with a solution that no longer causes the error, however it’s also no longer synchronous.

the code is expected to be executed on the application side. It could be injected via cy.window if required.

// store real observer
const RealResizeObserver = ResizeObserver;

let queueFlushTimeout;
let queue = [];

/**
 * ResizeObserver wrapper with "enforced batches"
 */
class ResizeObserverPolyfill {
	constructor(callback) {
		this.callback = callback;
		this.observer = new RealResizeObserver(this.check.bind(this));
	}

	observe(element) {
		this.observer.observe(element);
	}

	unobserve(element) {
		this.observer.unobserve(element);
	}

	disconnect() {
		this.observer.disconnect();
	}

	check(entries) {
		// remove previous invocations of "self"
		queue = queue.filter((x) => x.cb !== this.callback);
		// put a new one
		queue.push({ cb: this.callback, args: entries });
		// trigger update
		if (!queueFlushTimeout) {
			queueFlushTimeout = requestAnimationFrame(() => {
				queueFlushTimeout = undefined;
				const q = queue;
				queue = [];
				q.forEach(({ cb, args }) => cb(args));
			}, 0);
		}
	}
}

window.ResizeObserver = ResizeObserverPolyfill;

It fixed all my tests, so please give it a try.

I’ve got a case when Browser crashes into “Oh Snap” with a single test after performing a simple operation of opening a popup. The only change that aids a problem is adding CYPRESS_NO_COMMAND_LOG, nothing else helps. Also important to mention that the problem persists from Cypress v10 to v12 and v13.

According to this

  • the problem is not related to the amount of tests. It can happen with one test
  • the problem is not related to Cypress version. More likely it’s browser (as mentioned many times above)
  • the problem is related to Cypress functionality as disabling the command log alters behavior

We opted out to migrate V13+ because of this issue and we still encounter this issue trying to upgrade to V14.0.0 as we are now unable to use v12.17.4 due to having errors in GH workflows. The only solution for us currently is to slowly migrate to Playwright instead because of this long overdue problem.

I am having the same issue, it is crashing with Chrome 115 but if I download the stable 114 from here: https://chromium.cypress.io/mac/ and then run it with --browser [path to the downloaded chrome] it works.

This crash happens in two situations in my codebase since Chromium was upgraded to 111+:

  1. A multi-select from react-select inside a modal: If the modal is resized when an option is clicked to select (for example, the modal is rendering the selected options in a way that its height expands when there is a new selected option), Chromium crashes.
  2. Monaco editor for React is used, as reported by someone in StackOverflow.

Both are related to usages of ResizeObserver. In fact, if I run tests with ELECTRON_ENABLE_LOGGING=1, I can see “ResizeObserver loop completed with undelivered notifications.” logged before the crashes.

If I just remove react-select’s (floating-ui’s) usage of ResizeObserver (by locally patching https://github.com/JedWatson/react-select/blob/2a913698ad3d7759fb8e6bc5dd8a7d839227da2f/packages/react-select/src/components/Menu.tsx#L658 with { elementResize: false }), the crash no longer happens.

Disabling Cypress command log using CYPRESS_NO_COMMAND_LOG=1, as @Lasidar suggested in https://github.com/cypress-io/cypress/issues/27415#issuecomment-1778999153, worked for me as well, but it’s not practical in some situations, particularly when engineers rely on the command log in CI screenshots to debug.

The best workaround for my monaco-editor use case, so far, is the polyfill suggested by @theKashey in https://github.com/cypress-io/cypress/issues/27415#issuecomment-2169155274. It worked in my codebase and was simple to implement. Since I’m using cucumber, I annotated tests that need the polyfill with @polyfillResizeObserver and just added this to steps.ts:

// ResizeObserverPolyfill code here

Before({ tags: "@polyfillResizeObserver" }, () => {
  cy.on("window:before:load", (win) => {
    win.ResizeObserver = ResizeObserverPolyfill;
  });
});

I really hope Cypress is able to provide a real fix as soon as possible.

Hello Guys, We keep facing this issue all the time, with the latest cypress version 14.0.3 , the number of times we get it has increased a lot. previously we used 13.17 .0 we are using experimentalMemoryManagement: true, however even this doesnt help sometimes it takes us to retigger the test 5 times, to make it pass. the issue happens mostly when tests are run on the gitlab ci , however sometimes, also when running locally

I was able to reproduce this with the code below. Setting experimentalMemoryManagement did not help. I was running in docker on a cypress/included 13.13.1 image, but the resources were pretty reasonable. CPU: 16, Mem: 7GB. Ran in Chrome 127

var i = 0;
for (i = 0; i < 500 ; i++) {    
  it('Yeah - ' + i, () => {
    cy.visit('https://www.google.com/');
  });
}

Screenshot 2024-07-30 at 11 47 13 AM

Edit: Simplifying code example

I tested it in the homolog environment, I encountered this error. Interestingly, the button who causes the crash it works perfectly outside of Cypress, and I have tested it in various scenarios with cypress. The version of Cypress used is 12.7.0.

Here are the details of the environments where the issue occurred:

3. Environment: macOS Ventura version 13.1 (22C65)
   Browser: Chrome - Version 115.0.5790.114 (Versão oficial) (arm64)
   Result: Didn't work

4. Environment: Ubuntu
   Browser: Chrome - Version 113.0.5672.126
   Result: Worked fine

5. Also tested it in our pipeline, and it worked without any issues. The Docker image used was `cypress/browsers:node16.14.2-slim-chrome100-ff99-edge`.

I suspect that the Chrome version 115 might be causing the problem, possibly due to memory leaks or other issues, idk, just guessing so far. Additionally, in the Electrum application, after clicking the specific button he shows in the cypress console one of the following error messages:

1. ResizeObserver loop limit exceeded;

2. ResizeObserver loop completed with undelivered notifications.

Wich i already fixed way back then with Cypress.on("uncaught:exception")

Unfortunately, this is all the information I currently have, as I haven’t had enough time to investigate further. And i tried the workaround, sadly didn’t work. So far my workaround is gonna be work on electron.

I want to bring everyone’s attention back to the ResizeObserver loop error + Chrome 115+ combination. I have in my case 100% identified it as the source of the problem. What I have:

  • a spec file with 30 tests
  • each test triggers a “ResizeObserver loop completed with undelivered notifications” error exactly once on page load
  • the error is ignored in Cypress’ unhandled rejection listener
  • after 25 tests or so the Chrome Renderer process crashes, starting in Chrome 115
  • fixing the ResizeObserver error in the app fixes the spec run

So whatever happened in Chrome 115, it combines with Cypress to cause the renderer crash. Maybe something leaks when the error is silenced in the unhandled rejection handler.

I suspect that many of the reports here are resizeObserver related, because these errors happen frequently and are frequently hidden.

@Lasidar I’m not sure, we’d have to spend some more time investigating.

@akondratsky I’m in the same boat, I run my tests on Azure runners (Ubuntu + Electron 106) on Cypress 13.1.0 with 16GB of memory and they still crash that is ridiculous ! I enabled everything they said numTestsKeptInMemory: 0, experimentalMemoryManagement: true,

@nagash77 Any news on this ongoing issue ?

I started to have the same problem this week. Already tried your solution on cypress.config.ts, with --max_old_space_size=4096. And still crash on a specific element. He crashes in Chrome and Edge, but work’s fine in electron.

Just sharing that I have had success with disabling the command log / runner UI.

My tests were crashing out intermittently, but in specific places, but I wasn’t really seeing any dramatic memory increase. After upgrading some packages in the product-under-test they started crashing out in the specific places every time. Disabling the command log seems to have fixed it - though I don’t know if this is directly fixing things or just indirectly lowering the overall load on the system.

Cypress: 13.15.0 (but happening on previous versions too) Node: 20.12.2 OS: Windows 11 Pro

In our case, the crashes occurred largely due to the cypress-plugin-api plugin (details of the issue here: https://github.com/filiphric/cypress-plugin-api/issues/135).

I’m sure there’s possible workarounds to disable it in headless mode, but since this plugin isn’t crucial for us, we have decided to remove it altogether and so the performance of our tests has drastically improved!

Big kudos to @jennifer-shehane for investigating & helping to get to the bottom of this! 🙌

I just started performance tracing before AwwSnap and here is the last thing it recorded. Can it be really related to managing exceptions?

The last error is “ResizeObserver loop completed with undelivered notifications.” 😉

image

New findings:

if you have cypress test running via cypress open and chrome browser is in focus, it will crash 100/100 with the log sidebar enabled, but if you switch to another app (aka cmd/alt + tab) and then return to the chrome controlled by cypress, renderer process doesn’t crash and you’ll see the result

I’m getting this error for the first time We detected that the Chromium Renderer process just crashed. Cypress v 12.18

@Lasidar, thanks for your follow-ups on this issue, it’s helpful.

I’d like to add my 2 cents to all this. We have recently come across this problem having such a setup:

  • Cypress v13.2.0
  • Running in Jenkins within Docker in cypress/included:13.2.0
  • Chrome 116
  • Running in 4 parallel stages on the same node as Jenkins Example
  • AWS EC2 instance with 1) Linux Debian 2) 4 CPU 3) 15 RAM
  • Running time 1.50 mins for ±400 E2E auto-tests

When we set this all up we even could not run this concurrency cause ran into “We detected that the Chromium Renderer process just crashed.”

What helped us to fix it?

  1. We noticed that we have an enormous amount of logging and stdout outputting for DB actions. The most heavy for the system was console.log() with JSON.Stringify. Outputting a large string with JSON.stringify to the terminal console increases memory consumption, especially if the string being converted to JSON is large.
  2. Turn off stdout (debug query outputting) for DB actions

Unfortunately, I haven’t noticed any change after adding experimentalMemoryManagement or CYPRESS_NO_COMMAND_LOG=1 cypress run. In addition to this, when watching Test reply I noticed that all commands are still visualized and present on the right side of Cypress Test Runner. I assumed that it must disappear, maybe I did not get the final result of this flag.

Currently, I can’t tell that this error is a Bug as we usually understand it but rather inefficient memory management or just a heavy load that corresponds to the actual required good Cypress performance that currently can be easily fixed by just aligning your workload with the hardware requirements of your instance.

I can easily provide a reproducible project where addition plus one concurrent stream to my (4 stages x 4 CPU) parallelization setup will produce this error right away. But firstly, look at this performance analysis on a server, monitored by me during Cypress parallel run where we can see huge overloading of CPU by:

  • Cypress config manager or Cypress itself
  • Chrome

Maybe this will give some way forward for some of us. Result 1 Result 2 Result 3 Result 4 Result 5

Hello, thanks for answering. Running tests on Firefox is not an option for us as application UI is a bit different for Firefox and lot of extra changes will be done in automation code.

The only other option I can suggest in that case is to try disabling the cypress sidebar https://docs.cypress.io/guides/references/troubleshooting#Disable-the-Command-Log

Others above have also had luck downgrading to chrome 109 or earlier.

Our team faced this issue, too. We use Cypress 12.17.4 with Electron, and all tests run in the Docker container (built on top of the CentOS image). We tried suggestions from the article Fixing Cypress errors part 1: chromium out of memory crashes, but none of them helped (we did not check Chromium option).

It is worth noting that issue appears only on one machine. Three of the other works fine, without crashes at all. Same image, being run in our Jenkins pipeline, also works smoothly. We’ve already checked our Docker configurations - they are the same. All machines except Jenkins agent under the MacOS. And it is obvious that different processors also do not play a crucial role here.

I wonder what can be the difference here. If anyone has any idea what we can check - please ping me. We will return to investigating tomorrow.

I meet this issue when exec cypress run, but works on cypress open, so I specify the runner as Chrome, not Electron 130 by default. now it works.

package.json

{
	scripts: {
		"e2e": "cypress run --browser chrome"
	}
}

https://github.com/cypress-io/cypress/issues/27415#issuecomment-2258782755 Try this with your fix and see if it’s still happening.

Just sharing that I have had success with disabling the command log / runner UI.

My tests were crashing out intermittently, but in specific places, but I wasn’t really seeing any dramatic memory increase. After upgrading some packages in the product-under-test they started crashing out in the specific places every time. Disabling the command log seems to have fixed it - though I don’t know if this is directly fixing things or just indirectly lowering the overall load on the system.

Cypress: 13.15.0 (but happening on previous versions too) Node: 20.12.2 OS: Windows 11 Pro

Weighing in to say that (after trying almost all other suggested solutions) this also seemed to solve the problem for us in Cypress 14.0.1 where a test was consistently causing Electron/Chrome to crash in run mode due to (difficult to avoid) Resize Observer issues.

@oatsoda - there are many solutions. I would suggest running that code via before:load

cy.on('window:before:load', (win) => {
     ... // patch code
     win.ResizeObserver = ResizeObserverPolyfill;
  })

The fix for ResizeObserver I’ve posted above (#27415 (comment)) has solved almost all problems for us, but not absolutely all.

We all do observe the same behaviour of Cypress/Chrome crashing, but likely there is more than one reason underneath.

fwiw this did not solve my problem.

Hello @jennifer-shehane

Is there any update on this issue?

We are experiencing the same memory crash problem while running our tests in CI. I have tried all the solutions suggested here (and in other sources), but I am still facing the issue. The error occurs roughly one out of every three runs.

Since our project is open-source, I can also share the action link where the error occurs. MemoryCrashAction

We started getting this memory leaks issue after upgrading to cypress version from 12.17.4 to 13.13.0. We were encountering memory leak issues due to a forEach function we used, it’s likely because the function might be handling a large number of elements or performing complex operations repeatedly, causing memory build-up over time. Cypress tests can be sensitive to resource management, especially when dealing with DOM manipulations, network requests, or state management.

Avoid Chaining Too Many Commands Inside Loops If you are chaining multiple commands like cy.get, cy.click, or others inside a loop, this can cause the memory to spike

// Instead of this:

for (let i = 0; i < elements.length; i++) {
  cy.get(elements[i]).click().t').should('be.visible'); // Memory intensive
}

// Use flattened chain of commands:

elements.forEach((element) => {
  cy.get(element).then(($el) => {
    cy.wrap($el).click().type('text');
  });
});

Refactoring the tests which were causing this issue with the above use of flattened chain of commands worked for us, And we stopped getting the memory leak crashes.

We have a reproducible example of one user’s test suite running out of memory and are investigating where the memory leak could be right now. I can’t gaurantee that’s everyone’s problem, but we are doing that now.

My crash was coming from the new (at the time) Test Replay and the amount of network requests we were making. I noticed that the crash never happened on my logged out tests and then started looking at all of the analytic calls that are made when authenticated. So I started blocking the requests that were unnecessary to our E2E suite and the crashes vanished.

@jennifer-shehane the issue is still reliably reproducible using the repo I previously provided. I upgraded to Cypress 13.13.0 and added new logs accordingly: https://github.com/Lasidar/cypress-memory-crash-repro

Having previously been able to reproduce this relatively consistently in our app’s Cypress e2e tests, I am no longer able to reproduce this issue in our system in chrome 126, Cypress 13.11.0. I don’t see anything changed in our codebase that might have been fixed to resolve this so perhaps a chrome / cypress bug was since resolved.

It would be good if anyone else seeing this consistently could also check against these latest versions

Confirmed - pausing test before the failure point and removing error handlers solves the problem

image

I tested it in the homolog environment, I encountered this error. Interestingly, the button who causes the crash it works perfectly outside of Cypress, and I have tested it in various scenarios with cypress. The version of Cypress used is 12.7.0. Here are the details of the environments where the issue occurred:

3. Environment: macOS Ventura version 13.1 (22C65)
   Browser: Chrome - Version 115.0.5790.114 (Versão oficial) (arm64)
   Result: Didn't work

4. Environment: Ubuntu
   Browser: Chrome - Version 113.0.5672.126
   Result: Worked fine

5. Also tested it in our pipeline, and it worked without any issues. The Docker image used was `cypress/browsers:node16.14.2-slim-chrome100-ff99-edge`.

I suspect that the Chrome version 115 might be causing the problem, possibly due to memory leaks or other issues, idk, just guessing so far. Additionally, in the Electrum application, after clicking the specific button he shows in the cypress console one of the following error messages:

1. ResizeObserver loop limit exceeded;

2. ResizeObserver loop completed with undelivered notifications.

Wich i already fixed way back then with Cypress.on("uncaught:exception") Unfortunately, this is all the information I currently have, as I haven’t had enough time to investigate further. And i tried the workaround, sadly didn’t work. So far my workaround is gonna be work on electron.

I want to bring everyone’s attention back to the ResizeObserver loop error + Chrome 115+ combination. I have in my case 100% identified it as the source of the problem. What I have:

  • a spec file with 30 tests
  • each test triggers a “ResizeObserver loop completed with undelivered notifications” error exactly once on page load
  • the error is ignored in Cypress’ unhandled rejection listener
  • after 25 tests or so the Chrome Renderer process crashes, starting in Chrome 115
  • fixing the ResizeObserver error in the app fixes the spec run

So whatever happened in Chrome 115, it combines with Cypress to cause the renderer crash. Maybe something leaks when the error is silenced in the unhandled rejection handler.

I suspect that many of the reports here are resizeObserver related, because these errors happen frequently and are frequently hidden.

We had previously come to the same conclusion after investigation and have a ticket on our dev backlog to review the use of ResizeObserver. We’ve long had the test runner disabled because of this issue so it hasn’t been prioritised but below are some notes from the investigation.

In our React application codebase users can search for items and the results are displayed in a table. There is an implementation to perform resizing on this table’s headers. It’s used to slightly adjust the column header positions on the table based on whether there is scrollbar or not present in the results. As the user types to search, the results can filter. During a Cypress test where the the results are filtered down by typing and the scrollbar eventually disappears, the test can often crash with Aw, Snap! error in chrome. This is not seen by users and only in Cypress testing. Adding time between keystrokes reduced but didn’t fully prevent the issue from happening. In testing, we added 2 second delays between each key stroke, but at the point of the browser would still crash.

Wrapping the ResizeObserver code in a setTimeout (like below) appears to prevent the issue of Cypress crashing however this breaks the the table resizing so a review of the implementations is required. image

This resize observer error was dismissed initially as researching questions of similar issue described it as benign and even included code snippets to ignore this error in Cypress. This error does not happen in Firefox. Cypress crash issue has been happening since Chrome 115 and was not happening when downgraded to v114.

Anyone tried an old tip from Gleb using the garbage collector after each test? ctrl + f + gc

https://glebbahmutov.com/blog/cypress-tips-and-tricks/

@jennifer-shehane

We’ll need to do more investigation to determine if the issue is with the cucumber plugin itself or with how we are handling custom preprocessors. I have heard of issues in the past with the cucumber plugin performance.

I don’t have any custom preprocessors in my project and I’m facing this chromium renderer crashing issue almost half a year now. I’ve tried all solutions from this thread and nothing really solves the issue.

The only thing that kind of works is splitting up specs. For example, I had a spec with 10 tests that were running without any problems with older Cypress versions (below 12). Now I have 2 specs with 5 tests and they are still occasionally crashing. I don’t think that dividing them further is really solving anything, it’s just a workaround that crates a mess in repository.

Unfortunately I cannot share link to my project

@Lasidar Thank you for providing a reproducible example. We are able to reproduce the Chromium renderer crashing with this example.

We believe the memory usage in your example is coming from the use of the cucumber-preprocessor plugin. We removed the custom preprocessor and created an equivalent spec and were able to run that spec without the memory crash. The memory hit the 50% threshold and then went down as expected with experimentalMemoryManagement. In the cucumber spec, the memory kept climbing indicating some sort of memory leak.

We’ll need to do more investigation to determine if the issue is with the cucumber plugin itself or with how we are handling custom preprocessors. I have heard of issues in the past with the cucumber plugin performance.

This doesn’t offer a great solution in the interim of us investigating. One could remove the cucumber-preprocessor, but I know this is a big business decision with other ramifications.

Can confirm that Chrome is still crashing for me on Chrome 118 with Cypress 13.4.0 (cypress/browsers image tag cypress/browsers:node-20.9.0-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1).

I have updated Chrome version to latest (118) with Cypress 13 and resolved problem with crash.