You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Report a memory issue found while using Cypress.
3
+
body:
4
+
- type: markdown
5
+
attributes:
6
+
value: |
7
+
Have a question? 👉 [Ask in chat](https://on.cypress.io/discord) or [start a new discussion](https://github.com/cypress-io/cypress/discussions).
8
+
9
+
Prior to logging a memory issue, please make sure you are running the latest version of Cypress and have enabled [`experimentalMemoryManagement`](https://on.cypress.io/experiments) for Chromium-based browsers (introduced in Cypress 12.4.0).
10
+
11
+
If you are running in `cypress open` mode, you can also try lowering [`numTestsKeptInMemory`](https://docs.cypress.io/guides/references/configuration#Options) in your config file.
12
+
13
+
If you are still experiencing the issue, please fill out the following information.
14
+
- type: textarea
15
+
id: reproduction
16
+
attributes:
17
+
label: Test code to reproduce
18
+
description: Please provide a failing test or repo we can run. You can fork [this repo](https://github.com/cypress-io/cypress-test-tiny), set up a failing test, then link to your fork. If you have never done this before, watch [this video](https://youtu.be/NnriKHmj5T8) for example.
19
+
placeholder: Here is my failing test code and the app code to run the tests on...
20
+
validations:
21
+
required: true
22
+
- type: dropdown
23
+
id: mode
24
+
attributes:
25
+
label: Cypress Mode
26
+
description: What mode of Cypress are you running?
27
+
options:
28
+
- cypress run
29
+
- cypress open
30
+
- both modes
31
+
validations:
32
+
required: true
33
+
- type: input
34
+
id: version
35
+
attributes:
36
+
label: Cypress Version
37
+
description: What version of Cypress are you running? Run `cypress version` to see your current version. If possible, please update Cypress to the latest version first.
38
+
placeholder: ex. 10.3.1
39
+
validations:
40
+
required: true
41
+
- type: input
42
+
id: browser
43
+
attributes:
44
+
label: Browser Version
45
+
description: What browser(s) is Cypress running against when you are encountering your problem? The more specific the better. ie Chrome 109.0.5414.87 or Firefox 107.0
46
+
placeholder: ex. Chrome 109.0.5414.87
47
+
validations:
48
+
required: true
49
+
- type: input
50
+
id: node-version
51
+
attributes:
52
+
label: Node version
53
+
description: What version of node.js are you using to run Cypress?
54
+
placeholder: ex. v16.16.0
55
+
validations:
56
+
required: true
57
+
- type: input
58
+
id: os
59
+
attributes:
60
+
label: Operating System
61
+
description: What operating system is Cypress running on when you are encountering your problem? The more specific the better. ie macOS 12.4 or Windows 10.0.19044.1889
62
+
placeholder: ex. macOS 12.4
63
+
validations:
64
+
required: true
65
+
- type: textarea
66
+
id: debug-logs
67
+
attributes:
68
+
label: Memory Debug Logs
69
+
description: |
70
+
If running a Chromium-based browser, please set the `CYPRESS_INTERNAL_MEMORY_SAVE_STATS` environment variable to `1` or `true` and include the `cypress\logs\memory\<spec name>.json` file here.
71
+
72
+
Alternatively, you can run Cypress in [debug mode](https://docs.cypress.io/guides/references/troubleshooting#Print-DEBUG-logs) setting `DEBUG=cypress*memory` and include the entire set of logs here.
0 commit comments