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

CI fails due to Chromium Renderer process crashes on Cypress Cloud #25063

Closed
luixxiul opened this issue Apr 7, 2023 · 3 comments
Closed

CI fails due to Chromium Renderer process crashes on Cypress Cloud #25063

luixxiul opened this issue Apr 7, 2023 · 3 comments
Labels
A-Developer-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect Z-Flaky-Test A test is raising false alarms

Comments

@luixxiul
Copy link

luixxiul commented Apr 7, 2023

Steps to reproduce

https://cloud.cypress.io/projects/ppvnzg/runs/12024/specs shows that a couple of the tests have failed as the Chromium Renderer process crashed. Here is the log displayed on the page above.

Incomplete

    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.
        - Try enabling experimentalMemoryManagement in your config file.
        - Try lowering numTestsKeptInMemory in your config file.
    - You are running in a memory starved VM environment.
        - Try enabling experimentalMemoryManagement in your config file.
        - Try lowering numTestsKeptInMemory in your config file.
    - There are problems with your GPU / GPU drivers
    - There are browser bugs in Chromium

    You can learn more including how to fix Docker here:

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

    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.
        - Try enabling experimentalMemoryManagement in your config file.
        - Try lowering numTestsKeptInMemory in your config file.
    - You are running in a memory starved VM environment.
        - Try enabling experimentalMemoryManagement in your config file.
        - Try lowering numTestsKeptInMemory in your config file.
    - There are problems with your GPU / GPU drivers
    - There are browser bugs in Chromium

    You can learn more including how to fix Docker here:

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

2 of 42 specs skipped

https://cloud.cypress.io/projects/ppvnzg/runs/12026/specs shows the same error as well.

I am not sure how to reproduce the error consistently on Cypress Cloud, while I notice the same issue often happens on a local machine with 6GB RAM when it runs timeline.spec.ts tests.

Maybe related to element-hq/element-desktop#680?

Outcome

What did you expect?

The test should complete.

What happened instead?

The test was incomplete due to the issue described above.

Operating system

No response

Browser information

No response

URL for webapp

No response

Application version

No response

Homeserver

No response

Will you send logs?

No

@luixxiul
Copy link
Author

luixxiul commented Apr 7, 2023

I suspect this kind of issue would happen more frequently once we have added more E2E tests.

@luixxiul luixxiul changed the title Chromium Renderer process crashed on Cypress Cloud CI fails due to Chromium Renderer process crashes on Cypress Cloud Apr 12, 2023
@weeman1337 weeman1337 added Z-Flaky-Test A test is raising false alarms A-Developer-Experience S-Minor Impairs non-critical functionality or suitable workarounds exist O-Occasional Affects or can be seen by some users regularly or most users rarely labels Apr 20, 2023
@luixxiul
Copy link
Author

I have not noticed a similar issue recently. I am going to close this for now. Will reopen if I started seeing the issue again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Developer-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect Z-Flaky-Test A test is raising false alarms
Projects
None yet
Development

No branches or pull requests

2 participants