question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The Chromium Renderer process just crashed - 'sad face' Error

See original GitHub issue

Hi, I am running m cypress script in headless mode on a remote ubuntu 18.03 machine. The strange thing is that it works fine on my local macbook, but I’m getting an error that the Chromium renderer is crashing when running on the ubuntu server. Here is the output:

We detected that the Chromium Renderer process just crashed.
[1] 
[1] This is the equivalent to seeing the 'sad face' when Chrome dies.
[1] 
[1] This can happen for a number of different reasons:
[1] 
[1] - You wrote an endless loop and you must fix your own code
[1] - There is a memory leak in Cypress (unlikely but possible)
[1] - You are running Docker (there is an easy fix for this: see link below)
[1] - You are running lots of tests on a memory intense application
[1] - You are running in a memory starved VM environment
[1] - There are problems with your GPU / GPU drivers
[1] - There are browser bugs in Chromium
[1] 
[1] You can learn more including how to fix Docker here:
[1] 
[1] https://on.cypress.io/renderer-process-crashed
[1] TypeError: onError is not a function
[1]     at BrowserWindow.onCrashed (/home/ubuntu/.cache/Cypress/4.4.0/Cypress/resources/app/packages/server/lib/modes/run.js:538:7)
[1]     at WebContents.<anonymous> (/home/ubuntu/.cache/Cypress/4.4.0/Cypress/resources/app/packages/server/lib/gui/windows.js:181:34)
[1]     at WebContents.emit (events.js:215:7)
[1] 
[1] TypeError: onError is not a function
[1]     at BrowserWindow.onCrashed (/home/ubuntu/.cache/Cypress/4.4.0/Cypress/resources/app/packages/server/lib/modes/run.js:538:7)
[1]     at WebContents.<anonymous> (/home/ubuntu/.cache/Cypress/4.4.0/Cypress/resources/app/packages/server/lib/gui/windows.js:181:34)
[1]     at WebContents.emit (events.js:215:7)
[1] 
[1] The Test Runner unexpectedly exited via a exit event with signal SIGILL
[1] 
[1] Please search Cypress documentation for possible solutions:
[1] 
[1] https://on.cypress.io
[1] 
[1] Check if there is a GitHub issue describing this crash:
[1] 
[1] https://github.com/cypress-io/cypress/issues
[1] 
[1] Consider opening a new issue.
[1] 
[1] ----------
[1] 
[1] Platform: linux (Ubuntu Linux - 18.04)
[1] Cypress Version: 4.4.0

Is there any way for me to see why it is crashing? 🤔

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:18 (5 by maintainers)

github_iconTop GitHub Comments

7reactions
jennifer-shehanecommented, Jul 9, 2020

Unfortunately we’ll have to close this issue if there is not enough information to reproduce the problem. This does not mean that your issue is not happening - it just means that we do not have a path to move forward.

There’s a lot of things that could contribute to the browser crashing, including issues from the underlying application under test that don’t have to do with Cypress. Please comment in this issue with a reproducible example so we can assess that this is an issue specific to Cypress.

4reactions
zac11commented, May 7, 2020

@JimLynchCodes Did you try the same tests in Chrome headless?

I disabled the shm usage as per the suggestion from @jennifer-shehane here #7200 and even then Electron would crash and the Chromium renderer error would be thrown.

I changed the run command to have --headless --browser chrome and now the tests are running fine. Can you check if your tests fail on Chrome too?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Chromium Renderer process just crashed on Jenkins
We detected that the Chromium Renderer process just crashed. This is the equivalent to seeing the 'sad face' when Chrome dies.
Read more >
cypress-io/cypress - Gitter
We detected that the Chromium Renderer process just crashed. This is the equivalent to seeing the 'sad face' when Chrome dies. This can...
Read more >
Fixing Cypress errors part 1: chromium out of memory crashes
Solution 1: Use --ipc=host Docker flag​​ Luckily, we have a found a simple one line fix for this problem - simply add the...
Read more >
Pipelines crash caused by shared memory size change (/dev ...
The shared memory size was changed last week from 512mb to 64mb making CI tests using puppeteer/wdio with chrome headless unable to run....
Read more >
How to set up a runner in the cloud for GitLab.com to solve out ...
We detected that the Chromium Renderer process just crashed. This is the equivalent to seeing the 'sad face' when Chrome dies.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found