Thanks for connecting us <@697794951198801920>!
<@...
# helpa
adventurous-dream-20049
06/30/2022, 2:16 PMThanks for connecting us @fresh-doctor-14925!
@agreeable-painting-90494 Can you confirm if you are using the latest Cypress version (10.3) which which includes a bug-fix for memory leaks in Chromium-based browsers?
https://docs.cypress.io/guides/references/changelog#10-3-0
a
agreeable-painting-90494
06/30/2022, 2:17 PMYep, 10.3.0
agreeable-painting-90494
06/30/2022, 2:18 PMI'm trying now with memory set to 8g in the runner advanced config
agreeable-painting-90494
06/30/2022, 2:22 PM(for docker btw)
a
adventurous-dream-20049
06/30/2022, 2:24 PMA few questions:
- Is this issue happening locally, in CI, or both?
- If you are running parallel, how many machines/agents/runners/nods do you have allocated for parallel jobs to utilize?
- What are the CPU and memory resources for the node(s)?
- Can you re-run Cypress in CI with debug mode enabled and attach the entire set of logs here? This may be as simple as updating your
cypress runNO_COLOR=1 DEBUG=cypress:* cypress runnpx cypress run --record --key <record key>DEBUG=cypress:* npx cypress run --record --key <record key>a
agreeable-painting-90494
06/30/2022, 2:27 PMI believe it is only in CI that we are having the problem. We have an Azure machine that has 64gig ram and 16 cores. There are 6 runners with 2 core for each and 8 gb allocated (it was previously set to whatever the default is)
agreeable-painting-90494
06/30/2022, 2:29 PMI ran the profiler DEBUG setting and ran it previously and when it stopped showing results it still showed the profiler information every 10 secs
agreeable-painting-90494
06/30/2022, 2:33 PMI'm hoping that the 8 gb will help, it'll take a couple of hours to run though, we have ~3000 tests
5 Views