Chromium Renderer 进程刚刚在 Jenkins 上崩溃

Question

在 Jenkins 上遇到这个问题。我已经运行 Cypress 一个月了，没有遇到任何问题。一旦我从5.3.0 更新版本-> 5.5.0 开始出现此问题。

注意：我的测试不在 docker 容器中。

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
- There is a memory leak in Cypress (unlikely but possible)
- 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

You can learn more including how to fix Docker here:

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

┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:      5.5.0                                                                            │
  │ Browser:      Electron 85 (headless)                                                           │
  │ Specs:        2 found (webapp/authenctication.js, webapp/booking.js)                           │
  │ Searched:     cypress/specs/webapp/authenctication.js, cypress/specs/webapp/booking.js         │
  │ Experiments:  experimentalFetchPolyfill=true,experimentalNetworkStubbing=true                  │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

Answer 1

自托管 GitLab 中存在同样的问题。这可能是因为内存不足。

以下解决方案可能会有所帮助：

1. 设置--disable-dev-shm-usage 选项：https://github.com/cypress-io/cypress/issues/350#issuecomment-633700002
2. 为您的 Jenkins 分配更多内存

Answer 2

通过在 Docker 容器中运行赛普拉斯测试解决了这个问题。