fix: Update Chrome renderer crash to be more terse and up to date (#26597)

Author: jennifer-shehane

cli/CHANGELOG.md

@@ -6,6 +6,7 @@ _Released 05/09/2023 (PENDING)_
 **Bugfixes:**
 
 - Fixed an issue in Electron where devtools gets out of sync with the DOM occasionally. Addresses [#15932](https://github.com/cypress-io/cypress/issues/15932).
+- Updated the Chromium renderer process crash message to be more terse. Addressed in [#26597](https://github.com/cypress-io/cypress/pull/26597).
 
 ## 12.11.0
 

packages/errors/__snapshot-html__/RENDERER_CRASHED.html

@@ -620,22 +620,14 @@ export const AllCypressErrors = {
     return errTemplate`\
         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.
 
-        This can happen for a number of different reasons:
+        If you're running lots of tests on a memory intense application.
+          - Try increasing the CPU/memory on the machine you're running on.
+          - Try enabling ${fmt.highlight('experimentalMemoryManagement')} in your config file.
+          - Try lowering ${fmt.highlight('numTestsKeptInMemory')} in your config file during 'cypress open'.
 
-        - 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 ${fmt.highlight('experimentalMemoryManagement')} in your config file.
-            - Try lowering ${fmt.highlight('numTestsKeptInMemory')} in your config file.
-        - You are running in a memory starved VM environment.
-            - Try enabling ${fmt.highlight('experimentalMemoryManagement')} in your config file.
-            - Try lowering ${fmt.highlight('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:
+        You can learn more here:
 
         https://on.cypress.io/renderer-process-crashed`
   },

packages/errors/src/errors.ts

@@ -20,22 +20,14 @@ exports['Browser Crash Handling / when the tab crashes in chrome / fails'] = `
 
 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.
 
-This can happen for a number of different reasons:
+If you're running lots of tests on a memory intense application.
+  - Try increasing the CPU/memory on the machine you're running on.
+  - Try enabling experimentalMemoryManagement in your config file.
+  - Try lowering numTestsKeptInMemory in your config file during 'cypress open'.
 
-- 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:
+You can learn more here:
 
 https://on.cypress.io/renderer-process-crashed
 
@@ -117,22 +109,14 @@ exports['Browser Crash Handling / when the tab crashes in electron / fails'] = `
 
 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.
 
-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
+If you're running lots of tests on a memory intense application.
+  - Try increasing the CPU/memory on the machine you're running on.
+  - Try enabling experimentalMemoryManagement in your config file.
+  - Try lowering numTestsKeptInMemory in your config file during 'cypress open'.
 
-You can learn more including how to fix Docker here:
+You can learn more here:
 
 https://on.cypress.io/renderer-process-crashed