Open nemonemi opened 5 months ago
If this keeps growing, we won't be able to simply crank up the memory limit, nor, in my opinion, should it be consuming so many resources for such a simple application/test suite.
@nemonemi Can you provide the simple test case for us to run and reproduce?
@jennifer-shehane, as stated at the beginning of the ticket, it is not.
If we understood what was causing the issue, then we would, perhaps, be able to resolve it ourselves or provide more information. If there is some other information that you need, that is missing here, please let me know how to obtain it, and it will be added to the ticket.
We need a way to run the code or similar code that reproduces this situation in order to debug.
For more details, I have referenced this ticket https://github.com/cypress-io/cypress/discussions/26175 which shows the same error.
If this one cannot be worked on, can at least the other one be resolved?
@nemonemi Thanks for linking that discussion.
This seems specific to Kubernetes with Chrome. Some previous discussions found:
Can someone provide a reproducible example? What repo to run + how it's being run. I have Kubernetes running on Docker desktop with a cypress/included 13.3.1 image. I'm running a series of tests that actually do crash Chrome do to the memory consumption, but I'm not seeing this permission error.
I have experienced this issue with electron as well
We have the same issue using Electron on Bitbucket Pipelines. Cypress for Vue Component testing. Only one test fails.
We'll need a repo to run in order to investigate.
This chromium issue is related: Suppress failed to trigger oom adjust warning on kubernetes by default
@joh-klein
This chromium issue is related: Suppress failed to trigger oom adjust warning on kubernetes by default
Thanks for providing that Chromium link! According to the last entry in that issue, the Chromium folks want to pass the issue back to Cypress.
Same happened with bitbucket pipelines. Config of pipeline:
image: cypress/browsers:node-20.14.0-chrome-126.0.6478.114-1-ff-127.0.1-edge-126.0.2592.61-1
pipelines:
default:
- step:
caches:
- npm
- cypress
- node
script:
- npm install
- npx cypress install
- npm run start:ci
- npm run test:ci
artifacts:
- cypress/screenshots/**
- cypress/videos/**
definitions:
caches:
npm: $HOME/.npm
cypress: $HOME/.cache/Cypress
Seeing same issue here as well cypress v11
We are encountering the same error while running in a self-hosted environment using actions-runner-controller/actions-runner-controller
.
Cypress: 13.15.0
Browser: Chrome 130 (headless)
Node Version: v20.18.0 (/usr/local/bin/node)
Test code to reproduce
It is not possible for us to share the test and source code to reproduce.
One of the messages that seemed related is
Failed to adjust OOM score of renderer with pid 610. Permission denied.
, and I've noticed that there is an unresolved discussion here since more than a year ago.We have 20 tests that run sequentially. They are all small and isolated.
What we've observed is that memory consumption keeps increasing constantly, as it would appear, in steps.
This occurs, from the current investigation, around the 14th-16th test.
We are using NX and the command looks like this:
yarn nx affected --base=$NX_BASE --head=$NX_HEAD --target=e2e --configuration=development --deployUrl=./ --browser chrome --output-style=stream --parallel=false
And, here is an example of a test
Since this is an NX project, there are 3 libraries with Cypress in them, and this is how their configs look like:
And our Gitlab pipeline is configured with the following values:
Cypress Mode
cypress run
Cypress Version
13.6.6
Browser Version
Chrome 121.0.6167.160
Node version
18.20.3
Operating System
Ubuntu 22.04.3 LTS
Memory Debug Logs
Other
The debug logs were 3 times in size, so I had to truncate it to fit it here. This is the last part of it.