-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Kubernetes: Memory not getting released - Failed to adjust OOM score of renderer with pid 610. Permission denied. #29563
Comments
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. |
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 #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: |
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. |
Seeing same issue here as well cypress v11 |
We are encountering the same error while running in a self-hosted environment using Cypress: 13.15.0
Browser: Chrome 130 (headless)
Node Version: v20.18.0 (/usr/local/bin/node) |
Hello @jennifer-shehane We're encountering the same issue on Bitbucket Pipelines. I have built a reproduction repository: https://bitbucket.org/olivier-tille/repro-failing-cypress-tests/src/main/ Here is the failing build: https://bitbucket.org/olivier-tille/repro-failing-cypress-tests/pipelines/results/1 Any help with this would be greatly appreciated! Please let me know if I can help in any way. Thank you |
The repro pipeline fails with:
I was able to run the https://github.com/cypress-io/cypress-example-kitchensink repo under Bitbucket using
I also checked whether the problem goes away with Cypress 14.x beta, and that is not the case. There is no change after updating. Could you update your repo https://bitbucket.org/olivier-tille/repro-failing-cypress-tests and confirm that it runs locally, then report the results when you run it again in a Bitbucket pipeline? Does the "OOM" error message still appear to prevent the pipeline from running, or does the message appear and the pipeline is successful? Also, the original problem describes running under Kubernetes. Is your pipeline also running under Kubernetes? If not, then your issue is related but not identical. |
That’s right, OOM error doesn’t result in failed tests.. it still executes
successfully.
…On Fri, 13 Dec 2024 at 19:20, Mike McCready ***@***.***> wrote:
@olivier-lxo <https://github.com/olivier-lxo>
We're encountering the same issue on Bitbucket Pipelines. [437:1212/125803.148706:ERROR:zygote_host_impl_linux.cc(273)]
Failed to adjust OOM score of renderer with pid 610: Permission denied (13)
I have built a reproduction repository:
https://bitbucket.org/olivier-tille/repro-failing-cypress-tests/src/main/
Here is the failing build:
https://bitbucket.org/olivier-tille/repro-failing-cypress-tests/pipelines/results/1
The repro pipeline fails with:
Your project does not contain a default supportFile. We expect a file
matching cypress/support/component.{js,jsx,ts,tsx} to exist.
If a support file is not necessary for your project, set supportFile to
false.
https://on.cypress.io/support-file-missing-or-invalid
I was able to run the
https://github.com/cypress-io/cypress-example-kitchensink repo under
Bitbucket using cypress/browsers:22.12.0 and I also saw an error similar
to the following, displayed for every test, however it did not prevent the
tests from successfully running:
[9283:1213/150615.281481:ERROR:zygote_host_impl_linux.cc(279)] Failed to
adjust OOM score of renderer with pid 10741: Permission denied (13)
I also checked whether the problem goes away with Cypress 14.x beta, and
that is not the case. There is no change after updating.
Could you update your repo
https://bitbucket.org/olivier-tille/repro-failing-cypress-tests and
confirm that it runs locally, then report the results when you run it again
in a Bitbucket pipeline? Does the "OOM" error message still appear to
prevent the pipeline from running, or does the message appear and the
pipeline is successful?
Also, the original problem describes running under Kubernetes. Is your
pipeline also running under Kubernetes? If not, then your issue is related
but not identical.
—
Reply to this email directly, view it on GitHub
<#29563 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFKDNFFVX4B6GKG4KOTK6OT2FL3KLAVCNFSM6AAAAABIFWDTUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRGY4DGOBWHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Confirming that the OOM error is not the root cause of failing tests.
|
@MikeMcC399 I updated the docker image but still get the failing test. This time with a different, config-related error: https://bitbucket.org/olivier-tille/repro-failing-cypress-tests/pipelines/results/3 As you said, it doesn't seem like it fails due to that error but the tests do run and pass locally (both directly through npm as well as in the same docker image I'm using for the pipeline). This leads me to think that the OOM error and the test fail are related. As to your question regarding Kubernetes: I don't know what the underlying stack of Bitbucket Pipelines is. |
Your workflow log https://bitbucket.org/olivier-tille/repro-failing-cypress-tests/pipelines/results/3 shows:
There are multiple issues involved here. The first two issues are reproducible locally without Kubernetes or Docker:
I tend to think that the error |
I have published a working Cypress Component Test project which uses TypeScript to https://bitbucket.org/mikemcc399/cy-vite-5-ts-ct The pipeline log is on https://bitbucket.org/mikemcc399/cy-vite-5-ts-ct/pipelines/results/1 The run is successful, and it shows multiple issues:
The pipeline shows the issue: then other unrelated issues:
Given that the pipeline succeeds, this supports the suggestion that the following message should be classed as a "garbage error":
|
Thank you for your help @MikeMcC399 Adding the |
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.
The text was updated successfully, but these errors were encountered: