search

cypress-io / netlify-plugin-cypress

Runs Cypress end-to-end tests after Netlify builds the site but before it is deployed
https://www.cypress.io/blog/2020/03/30/run-cypress-tests-on-netlify-using-a-single-line/
MIT License
89 stars 39 forks source link

Out of memory Chromium crash #58

Closed ehmicky closed 3 years ago

ehmicky commented 4 years ago

Versions

Describe the bug Chromium crash with an out-of-memory bug.

Logs and screenshots

11:01:53 PM: ┌────────────────────────────────────────────────────┐
11:01:53 PM: │ 5. onPostBuild command from netlify-plugin-cypress │
11:01:53 PM: └────────────────────────────────────────────────────┘
11:01:53 PM: ​
11:01:53 PM: It looks like this is your first time using Cypress: 4.4.1
11:01:53 PM: 
11:01:53 PM: [21:01:53]  Verifying Cypress can run /opt/build/repo/node_modules/CypressBinary/4.4.1/Cypress [started]
11:01:59 PM: [21:01:59]  Verifying Cypress can run /opt/build/repo/node_modules/CypressBinary/4.4.1/Cypress [completed]
11:01:59 PM: 
11:01:59 PM: Opening Cypress...
11:02:05 PM: tput: No value for $TERM and no -T specified
11:02:05 PM: ================================================================================
11:02:05 PM:   (Run Starting)
11:02:05 PM:   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
11:02:05 PM:   │ Cypress:    4.4.1                                                                              │
11:02:05 PM:   │ Browser:    Electron 80 (headless)                                                             │
11:02:05 PM:   │ Specs:      2 found (accessibility.test.js, pdp_comforter.test.js)                             │
11:02:05 PM:   └────────────────────────────────────────────────────────────────────────────────────────────────┘
11:02:05 PM: ────────────────────────────────────────────────────────────────────────────────────────────────────
11:02:05 PM:   Running:  accessibility.test.js                                                           (1 of 2)
11:02:13 PM: 
11:02:14 PM:   Homepage accessibility test
11:02:16 PM:     ✓ Has no detectable accessibility violations on load (2743ms)
11:02:16 PM:   PDP accessibility tests
11:02:21 PM: 
    ✓ Has no detectable accessibility violations on load (4461ms)
11:02:21 PM:   2 passing (7s)
11:02:22 PM:   (Results)
11:02:22 PM:   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
11:02:22 PM:   │ Tests:        2                                                                                │
11:02:22 PM:   │ Passing:      2                                                                                │
11:02:22 PM:   │ Failing:      0                                                                                │
11:02:22 PM:   │ Pending:      0                                                                                │
11:02:22 PM:   │ Skipped:      0                                                                                │
11:02:22 PM:   │ Screenshots:  0                                                                                │
11:02:22 PM:   │ Video:        true                                                                             │
11:02:22 PM:   │ Duration:     7 seconds                                                                        │
11:02:22 PM:   │ Spec Ran:     accessibility.test.js                                                            │
11:02:22 PM:   └────────────────────────────────────────────────────────────────────────────────────────────────┘
11:02:24 PM:   (Video)
11:02:24 PM:   -  Started processing:  Compressing to 32 CRF
11:02:29 PM:   -  Finished processing: /opt/build/repo/cypress/videos/accessibility.test.js.mp4       (4 seconds)
11:02:29 PM: ────────────────────────────────────────────────────────────────────────────────────────────────────
11:02:29 PM:   Running:  pdp_comforter.test.js                                                           (2 of 2)
11:02:31 PM: 
11:02:31 PM:   Cloud PDP is functioning
11:02:32 PM:     ✓ Loads the cloud PDP (1487ms)
11:02:33 PM:     ✓ Properly renders the Nav Bar (432ms)
11:02:34 PM:     ✓ Hero Slider Exists, is enabled, and has proper amount of Images (190ms)
11:02:34 PM: 
    ✓ Size (variant) selectors exists (69ms)
11:02:35 PM: 
    ✓ Price exists, Size (variant) selectors update price (1866ms)
11:02:36 PM: [3548:0605/210236.742571:FATAL:memory.cc(22)] Out of memory. size=524288
11:02:37 PM: We detected that the Chromium Renderer process just crashed.
11:02:37 PM: 
11:02:37 PM: This is the equivalent to seeing the 'sad face' when Chrome dies.
11:02:37 PM: 
11:02:37 PM: This can happen for a number of different reasons:
11:02:37 PM: 
11:02:37 PM: - You wrote an endless loop and you must fix your own code
11:02:37 PM: - There is a memory leak in Cypress (unlikely but possible)
11:02:37 PM: - You are running Docker (there is an easy fix for this: see link below)
11:02:37 PM: - You are running lots of tests on a memory intense application
11:02:37 PM: - You are running in a memory starved VM environment
11:02:37 PM: - There are problems with your GPU / GPU drivers
11:02:37 PM: - There are browser bugs in Chromium
11:02:37 PM: 
11:02:37 PM: You can learn more including how to fix Docker here:
11:02:37 PM: 
11:02:37 PM: https://on.cypress.io/renderer-process-crashed
11:02:37 PM: TypeError: onError is not a function
11:02:37 PM:     at BrowserWindow.onCrashed (/opt/build/repo/node_modules/CypressBinary/4.4.1/Cypress/resources/app/packages/server/lib/modes/run.js:538:7)
11:02:37 PM:     at WebContents.<anonymous> (/opt/build/repo/node_modules/CypressBinary/4.4.1/Cypress/resources/app/packages/server/lib/gui/windows.js:181:34)
11:02:37 PM:     at WebContents.emit (events.js:215:7)
11:02:37 PM: TypeError: onError is not a function
11:02:37 PM:     at BrowserWindow.onCrashed (/opt/build/repo/node_modules/CypressBinary/4.4.1/Cypress/resources/app/packages/server/lib/modes/run.js:538:7)
11:02:37 PM:     at WebContents.<anonymous> (/opt/build/repo/node_modules/CypressBinary/4.4.1/Cypress/resources/app/packages/server/lib/gui/windows.js:181:34)
11:02:37 PM:     at WebContents.emit (events.js:215:7)
11:02:39 PM: ​
11:02:39 PM: ┌────────────────────────────────────────────────┐
11:02:39 PM: │ Plugin "netlify-plugin-cypress" internal error │
11:02:39 PM: └────────────────────────────────────────────────┘
11:02:39 PM: ​
11:02:39 PM:   Error message
11:02:39 PM:   Error: The Test Runner unexpectedly exited via a exit event with signal SIGILL
11:02:39 PM: ​
11:02:39 PM:   Please search Cypress documentation for possible solutions:
11:02:39 PM: ​
11:02:39 PM:   https://on.cypress.io
11:02:39 PM: ​
11:02:39 PM:   Check if there is a GitHub issue describing this crash:
11:02:39 PM: ​
11:02:39 PM:   https://github.com/cypress-io/cypress/issues
11:02:39 PM: ​
11:02:39 PM:   Consider opening a new issue.
11:02:39 PM: ​
11:02:39 PM:   ----------
11:02:39 PM: ​
11:02:39 PM:   Platform: linux (Ubuntu Linux - 16.04)
11:02:39 PM:   Cypress Version: 4.4.1
11:02:39 PM: ​
11:02:39 PM:   Plugin details
11:02:39 PM:   Package:        netlify-plugin-cypress
11:02:39 PM:   Version:        1.3.11
11:02:39 PM:   Repository:     git+https://github.com/cypress-io/netlify-plugin-cypress.git
11:02:39 PM:   npm link:       https://www.npmjs.com/package/netlify-plugin-cypress
11:02:39 PM:   Report issues:  https://github.com/cypress-io/netlify-plugin-cypress/issues
11:02:39 PM: ​
11:02:39 PM:   Error location
11:02:39 PM:   In "onPostBuild" event in "netlify-plugin-cypress" from netlify.toml and package.json
11:02:39 PM:       at /opt/build/repo/node_modules/cypress/lib/errors.js:190:15
11:02:39 PM:       at tryCatcher (/opt/build/repo/node_modules/bluebird/js/release/util.js:16:23)
11:02:39 PM:       at Promise._settlePromiseFromHandler (/opt/build/repo/node_modules/bluebird/js/release/promise.js:547:31)
11:02:39 PM:       at Promise._settlePromise (/opt/build/repo/node_modules/bluebird/js/release/promise.js:604:18)
11:02:39 PM:       at Promise._settlePromise0 (/opt/build/repo/node_modules/bluebird/js/release/promise.js:649:10)
11:02:39 PM:       at Promise._settlePromises (/opt/build/repo/node_modules/bluebird/js/release/promise.js:729:18)
11:02:39 PM:       at Promise._fulfill (/opt/build/repo/node_modules/bluebird/js/release/promise.js:673:18)
11:02:39 PM:       at Promise._resolveCallback (/opt/build/repo/node_modules/bluebird/js/release/promise.js:466:57)
11:02:39 PM:       at Promise._settlePromiseFromHandler (/opt/build/repo/node_modules/bluebird/js/release/promise.js:559:17)
11:02:39 PM:       at Promise._settlePromise (/opt/build/repo/node_modules/bluebird/js/release/promise.js:604:18)
11:02:39 PM:       at Promise._settlePromise0 (/opt/build/repo/node_modules/bluebird/js/release/promise.js:649:10)
11:02:39 PM:       at Promise._settlePromises (/opt/build/repo/node_modules/bluebird/js/release/promise.js:729:18)
11:02:39 PM:       at Promise._fulfill (/opt/build/repo/node_modules/bluebird/js/release/promise.js:673:18)
11:02:39 PM:       at Promise._resolveCallback (/opt/build/repo/node_modules/bluebird/js/release/promise.js:466:57)
11:02:39 PM:       at Promise._settlePromiseFromHandler (/opt/build/repo/node_modules/bluebird/js/release/promise.js:559:17)
11:02:39 PM:       at Promise._settlePromise (/opt/build/repo/node_modules/bluebird/js/release/promise.js:604:18)
11:02:39 PM: ​
11:02:39 PM:   Error properties
11:02:39 PM:   { known: true }

Link to the repo Private repository

bahmutov commented 4 years ago

Yeah, not sure what we can do about it without a repo to see and run. Does this happen on every run?

ehmicky commented 4 years ago

Yes, I understand. Unfortunately, that's all the information we have. This was the last build of that Site.

Note: it seems to me that error handling might be failing here as well: TypeError: onError is not a function.

bahmutov commented 4 years ago

True, onError is not a function is weird - can this project be run in 4.7.0?

ehmicky commented 4 years ago

Those errors are coming from our error monitoring tooling, not from the user reporting the problem, so we cannot unfortunately run/re-run those builds.

I can see though if this error is happening again and make sure the Cypress version is always <4.7.0.

SimeonUnder2 commented 4 years ago

We're also getting this in Netlify builds. But it magically worked one time in ten.

"cypress": "^4.12.0",
"netlify-plugin-cypress": "^1.4.1",
philschonholzer commented 4 years ago

Having the same problem:

"cypress": "^4.11.0",
"netlify-plugin-cypress": "^1.4.1",
1:04:20 PM: [1751:0807/130420.357593:FATAL:memory.cc(22)] Out of memory. size=393216
1:04:20 PM: We detected that the Chromium Renderer process just crashed.
1:04:20 PM: 
1:04:20 PM: This is the equivalent to seeing the 'sad face' when Chrome dies.
1:04:20 PM: 
1:04:20 PM: This can happen for a number of different reasons:
1:04:20 PM: 
1:04:20 PM: - You wrote an endless loop and you must fix your own code
1:04:20 PM: - There is a memory leak in Cypress (unlikely but possible)
1:04:20 PM: - You are running Docker (there is an easy fix for this: see link below)
1:04:20 PM: - You are running lots of tests on a memory intense application
1:04:20 PM: - You are running in a memory starved VM environment
1:04:20 PM: - There are problems with your GPU / GPU drivers
1:04:20 PM: - There are browser bugs in Chromium
1:04:20 PM: 
1:04:20 PM: You can learn more including how to fix Docker here:
1:04:20 PM: 
1:04:20 PM: https://on.cypress.io/renderer-process-crashed
abohannon commented 4 years ago

Running into the same issue. Fresh Cypress install with a one simple test.

I upped the node heap memory, but that didn't work.

NPM Script: "staging": "GATSBY_ENV=staging node --max-old-space-size=25600 ./node_modules/.bin/gatsby build",

Dev Dependencies:

"cypress": "^5.0.0",
"netlify-plugin-cypress": "^1.4.1",

Netlify Build Logs:

12:07:29 PM: (build.command completed in 11m 37.9s)
12:07:29 PM: ​
12:07:29 PM: ┌────────────────────────────────────────────────────┐
12:07:29 PM: │ 3. onPostBuild command from netlify-plugin-cypress │
12:07:29 PM: └────────────────────────────────────────────────────┘
12:07:29 PM: ​
12:07:29 PM: It looks like this is your first time using Cypress: 5.0.0
12:07:29 PM: [19:07:29]  Verifying Cypress can run /opt/build/repo/node_modules/CypressBinary/5.0.0/Cypress [started]
12:07:31 PM: [19:07:31]  Verifying Cypress can run /opt/build/repo/node_modules/CypressBinary/5.0.0/Cypress [completed]
12:07:31 PM: 
12:07:31 PM: Opening Cypress...
12:07:35 PM: ====================================================================================================
12:07:35 PM:   (Run Starting)
12:07:35 PM:   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
12:07:35 PM:   │ Cypress:    5.0.0                                                                              │
12:07:35 PM:   │ Browser:    Electron 83 (headless)                                                             │
12:07:35 PM:   │ Specs:      1 found (home_page_spec.js)                                                        │
12:07:35 PM:   └────────────────────────────────────────────────────────────────────────────────────────────────┘
12:07:35 PM: ────────────────────────────────────────────────────────────────────────────────────────────────────
12:07:35 PM:   Running:  home_page_spec.js                                                               (1 of 1)
12:07:38 PM: Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
12:07:38 PM: 
12:07:38 PM:   Home Page
12:07:40 PM: [16985:0820/190740.026997:FATAL:memory.cc(38)] Out of memory. size=9096960
12:07:40 PM: [16985:0820/190740.037819:FATAL:memory.cc(38)] Out of memory. size=9096960
12:07:40 PM: We detected that the Chromium Renderer process just crashed.
12:07:40 PM: 
12:07:40 PM: This is the equivalent to seeing the 'sad face' when Chrome dies.
12:07:40 PM: 
12:07:40 PM: This can happen for a number of different reasons:
12:07:40 PM: 
12:07:40 PM: - You wrote an endless loop and you must fix your own code
12:07:40 PM: - There is a memory leak in Cypress (unlikely but possible)
12:07:40 PM: - You are running Docker (there is an easy fix for this: see link below)
12:07:40 PM: - You are running lots of tests on a memory intense application
12:07:40 PM: - You are running in a memory starved VM environment
12:07:40 PM: - There are problems with your GPU / GPU drivers
12:07:40 PM: - There are browser bugs in Chromium
12:07:40 PM: 
12:07:40 PM: You can learn more including how to fix Docker here:
12:07:40 PM: 
12:07:40 PM: https://on.cypress.io/renderer-process-crashed
12:07:40 PM: We detected that the Chromium Renderer process just crashed.
12:07:40 PM: 
12:07:40 PM: This is the equivalent to seeing the 'sad face' when Chrome dies.
12:07:40 PM: 
12:07:40 PM: This can happen for a number of different reasons:
12:07:40 PM: 
12:07:40 PM: - You wrote an endless loop and you must fix your own code
12:07:40 PM: - There is a memory leak in Cypress (unlikely but possible)
12:07:40 PM: - You are running Docker (there is an easy fix for this: see link below)
12:07:40 PM: - You are running lots of tests on a memory intense application
12:07:40 PM: - You are running in a memory starved VM environment
12:07:40 PM: - There are problems with your GPU / GPU drivers
12:07:40 PM: - There are browser bugs in Chromium
12:07:40 PM: 
12:07:40 PM: You can learn more including how to fix Docker here:
12:07:40 PM: 
12:07:40 PM: https://on.cypress.io/renderer-process-crashed
12:07:41 PM:   (Results)
12:07:41 PM:   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
12:07:41 PM:   │ Tests:        0                                                                                │
12:07:41 PM:   │ Passing:      0                                                                                │
12:07:41 PM:   │ Failing:      1                                                                                │
12:07:41 PM:   │ Pending:      0                                                                                │
12:07:41 PM:   │ Skipped:      0                                                                                │
12:07:41 PM:   │ Screenshots:  0                                                                                │
12:07:41 PM:   │ Video:        true                                                                             │
12:07:41 PM:   │ Duration:     0 seconds                                                                        │
12:07:41 PM:   │ Spec Ran:     home_page_spec.js                                                                │
12:07:41 PM:   └────────────────────────────────────────────────────────────────────────────────────────────────┘
12:07:41 PM:   (Video)
12:07:41 PM:   -  Started processing:  Compressing to 32 CRF
12:07:42 PM:   -  Finished processing: /opt/build/repo/cypress/videos/home_page_spec.js.mp4           (0 seconds)
12:07:42 PM: ====================================================================================================
12:07:42 PM:   (Run Finished)
12:07:42 PM:        Spec                                              Tests  Passing  Failing  Pending  Skipped  
12:07:42 PM:   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
12:07:42 PM:   │ ✖  home_page_spec.js                          0ms        -        -        1        -        - │
12:07:42 PM:   └────────────────────────────────────────────────────────────────────────────────────────────────┘
12:07:42 PM:     ✖  1 of 1 failed (100%)                       0ms        -        -        1        -        -  
12:07:42 PM: ​
12:07:42 PM: ┌────────────────────────────────────────┐
12:07:42 PM: │ Plugin "netlify-plugin-cypress" failed │
12:07:42 PM: └────────────────────────────────────────┘
12:07:42 PM: ​
12:07:42 PM:   Error message
12:07:42 PM:   Error: Failed Cypress tests
12:07:42 PM:   1 test(s) failed
12:07:42 PM: ​
12:07:42 PM:   Plugin details
12:07:42 PM:   Package:        netlify-plugin-cypress
12:07:42 PM:   Version:        1.4.1
12:07:42 PM:   Repository:     git+https://github.com/cypress-io/netlify-plugin-cypress.git
12:07:42 PM:   npm link:       https://www.npmjs.com/package/netlify-plugin-cypress
12:07:42 PM:   Report issues:  https://github.com/cypress-io/netlify-plugin-cypress/issues
12:07:42 PM: ​
12:07:42 PM:   Error location
12:07:42 PM:   In "onPostBuild" event in "netlify-plugin-cypress" from netlify.toml and package.json
12:07:42 PM:       at processCypressResults (/node_modules/netlify-plugin-cypress/src/index.js:153:14)
12:07:42 PM:       at postBuild (/node_modules/netlify-plugin-cypress/src/index.js:183:3)
12:07:42 PM:       at async onPostBuild (/node_modules/netlify-plugin-cypress/src/index.js:254:7)
12:07:42 PM: ​
12:07:42 PM:   Resolved config
12:07:42 PM:   build:
12:07:42 PM:     command: yarn staging
12:07:42 PM:     commandOrigin: ui
12:07:42 PM:     environment:
12:07:42 PM:       - GATSBY_ELASTICSEARCH_PRIVATE_KEY
12:07:42 PM:       - GATSBY_ENV
12:07:42 PM:       - GATSBY_ERROR_HANDLING
12:07:42 PM:       - GATSBY_SENTRY_ENV
12:07:42 PM:       - NETLIFY_ENV
12:07:42 PM:       - REVIEW_ID
12:07:42 PM:       - RUBY_VERSION
12:07:42 PM:       - TRADES_HEALTH_API_KEY
12:07:42 PM:       - CYPRESS_CACHE_FOLDER
12:07:42 PM:       - TERM
12:07:42 PM:     publish: /opt/build/repo/public
12:07:42 PM:   plugins:
12:07:42 PM:     - inputs: {}
12:07:42 PM:       origin: config
12:07:42 PM:       package: netlify-plugin-cypress
sherlaimov-osdb commented 4 years ago

Has this been resolved for anyone?

Versions: "cypress": "^5.0.0", "netlify-plugin-cypress": "^1.3.11",

ERROR: [2545:0828/135916.735000:FATAL:memory.cc(38)] Out of memory. size=393216 We detected that the Chromium Renderer process just crashed. ... ...same as above :(

philschonholzer commented 4 years ago

Can I help in any way? As long as this issue is open, I can't add Cypress to Netlify.

mmclafferty commented 4 years ago

Experiencing the same issue - [2484:0916/181330.902910:FATAL:memory.cc(22)] Out of memory. size=6660096

yunntan commented 4 years ago

Facing the same issue since earlier today; all the tests pass and we face a crash error at the end [20616:0916/180652.651761:FATAL:memory.cc(22)] Out of memory. size=4608000 8:06:54 PM: We detected that the Chromium Renderer process just crashed.

Tried to revert back to old "passing" commit, no success. Tried "Clear cache and deploy site" - no success.

kamsar commented 3 years ago

Could this possibly be related to https://github.com/cypress-io/cypress/issues/350, since I think Netlify is running builds in containers?

alexjfno1 commented 3 years ago

Also having the same issue:

2:25:26 PM: [2300:1117/142526.344417:FATAL:memory.cc(40)] Out of memory. size=917504
2:25:26 PM: We detected that the Chromium Renderer process just crashed.

It seems to be happy with a fairly lightweight page but as soon as there is lots of images and resources being loaded it crashes.

CypressCecelia commented 3 years ago

I ran into this issue with the code at this repo: https://github.com/ceceliacreates/ceceliacreates-nuxt/tree/netlify-cypress

Retried multiple times and browser crashed each time.

criess commented 3 years ago

We are running into the same problem.

Is Netlify informed & aware of the problem as well? because @kamsar mentioned a docker solution from the "host" side there.

I was also not able to find docs on what the hard resource limits (memory/cpu/time) when building on Netlify are.

10:38:11 AM: Opening Cypress...
10:38:15 AM: Missing baseUrl in compilerOptions. tsconfig-paths will be skipped
10:38:16 AM: tput: No value for $TERM and no -T specified
10:38:16 AM: ====================================================================================================
10:38:16 AM:   (Run Starting)
10:38:16 AM:   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
10:38:16 AM:   │ Cypress:    5.5.0                                                                              │
10:38:16 AM:   │ Browser:    Electron 85 (headless)                                                             │
10:38:16 AM:   │ Specs:      6 found (e2e/appointment.test.js, e2e/confidentiality.test.js, e2e/contact.test.js │
10:38:16 AM:   │             , e2e/rating_flow.test.js, plugins/index.js, support/commands.js)                  │
10:38:16 AM:   └────────────────────────────────────────────────────────────────────────────────────────────────┘
10:38:16 AM: ────────────────────────────────────────────────────────────────────────────────────────────────────
[… REDACTED …]
10:38:58 AM: [2305:1222/093858.212728:FATAL:memory.cc(40)] Out of memory. size=28496
10:38:58 AM: We detected that the Chromium Renderer process just crashed.
10:38:58 AM: 
10:38:58 AM: This is the equivalent to seeing the 'sad face' when Chrome dies.
10:38:58 AM: 
10:38:58 AM: This can happen for a number of different reasons:
10:38:58 AM: 
10:38:58 AM: - You wrote an endless loop and you must fix your own code
10:38:58 AM: - There is a memory leak in Cypress (unlikely but possible)
10:38:58 AM: - You are running Docker (there is an easy fix for this: see link below)
10:38:58 AM: - You are running lots of tests on a memory intense application
10:38:58 AM: - You are running in a memory starved VM environment
10:38:58 AM: - There are problems with your GPU / GPU drivers
10:38:58 AM: - There are browser bugs in Chromium
10:38:58 AM: 
10:38:58 AM: You can learn more including how to fix Docker here:
10:38:58 AM: 
10:38:58 AM: https://on.cypress.io/renderer-process-crashed
10:38:58 AM: We detected that the Chromium Renderer process just crashed.
10:38:58 AM: 
10:38:58 AM: This is the equivalent to seeing the 'sad face' when Chrome dies.
10:38:58 AM: 
10:38:58 AM: This can happen for a number of different reasons:
10:38:58 AM: 
10:38:58 AM: - You wrote an endless loop and you must fix your own code
10:38:58 AM: - There is a memory leak in Cypress (unlikely but possible)
10:38:58 AM: - You are running Docker (there is an easy fix for this: see link below)
10:38:58 AM: - You are running lots of tests on a memory intense application
10:38:58 AM: - You are running in a memory starved VM environment
10:38:58 AM: - There are problems with your GPU / GPU drivers
10:38:58 AM: - There are browser bugs in Chromium
10:38:58 AM: 
10:38:58 AM: You can learn more including how to fix Docker here:
10:38:58 AM: 
10:38:58 AM: https://on.cypress.io/renderer-process-crashed
bahmutov commented 3 years ago

Cloned @CypressCecelia into https://github.com/bahmutov/ceceliacreates-nuxt

image

The plugin v1.7.0 prints the cypress info command

image

bahmutov commented 3 years ago

and then it crashes again

image

bahmutov commented 3 years ago

Added CircleCI and GH Actions builds to https://github.com/bahmutov/ceceliacreates-nuxt to compare - they run fine without crashing, only the Netlify plugin crashes.

Disabling video helped a little, but there are still crashes after a few tests

bahmutov commented 3 years ago

Added recording just to see how different CIs behave https://dashboard.cypress.io/projects/xn3ihk

Netlify pretty much always crashes, a gets cross-origin error #107

Screen Shot 2021-02-05 at 9 40 39 AM
bahmutov commented 3 years ago

Still crashes even when testing the deployed URL https://github.com/bahmutov/ceceliacreates-nuxt/pull/1

Screen Shot 2021-02-05 at 2 20 46 PM
erezrokah commented 3 years ago

Hello 👋 Would anyone be interested in testing a draft PR with a potential fix?

You can install it via npm i https://github.com/erezrokah/netlify-plugin-cypress#feat/use_chrome and add the following to netlify.toml

[[plugins]]
  package = "netlify-plugin-cypress"
bahmutov commented 3 years ago

Nice job @erezrokah I tested it in https://app.netlify.com/sites/ceceliacreates-nuxt/deploys/60219e9518a3950007bfc080 and it worked, it even records video fine https://dashboard.cypress.io/projects/xn3ihk/runs/90

Let me work on merging your PR, I think we should expose an option to use either Electron or Chromium. Also, I need to see where Chromium is cached - is it just stored in node_modules?

bahmutov commented 3 years ago

:tada: This issue has been resolved in version 1.9.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

erezrokah commented 3 years ago

Let me work on merging your PR, I think we should expose an option to use either Electron or Chromium. Also, I need to see where Chromium is cached - is it just stored in node_modules?

Looks like you figured everything out :) Yes it puts it under node_modules so it is cached. Thank you for moving so fast on this!

ehmicky commented 3 years ago

This is awesome, thanks @bahmutov and @erezrokah! :tada:

@bahmutov Would you like to make a new release on github.com/netlify/plugins?

bahmutov commented 3 years ago

@ehmicky I had a question about it - how often do we need to update your repo?

ehmicky commented 3 years ago

That repository is the list of plugins listed in the Netlify UI. New versions of plugins are available in the UI as soon as this file is updated. In most cases, just bumping the version field should be enough :+1: