tests/e2e/visual/wdio.conf.js, working on
issue #9917
with default above configuration, I am getting above error, if someone is familiar with above issue then please help me out with this.
running below command
npm run wdio-visual-desktop
EDIT: It worked on VM with more number of cores and RAM.
1 Like

Yeah, the wdio tests are comparatively resource intensive. They spin up a full CHT server deployment in docker containers as well as a Chrome instance. If the Chome tab is crashing, one cause could be that the resources are too constrained. Sounds like increasing the resources resolved this issue.
2 Likes
hey @jkuester that is one of the probable reason but also when you try to run npm run wdio-visual-desktop
back to back without giving much break it will also throw that error so I had to write a shell script to delete the process related to chrome and deleting temporary data directories
1 Like