Open joshua-redmond opened 8 months ago
Hi! Here's something I've noticed:
Every time a test starts up, Chrome creates two folders under /tmp/:
/tmp/
/tmp/.com.google.Chrome.PyT0E2
/tmp/.org.chromium.Chromium.OBIvvs
Though both folders are left behind when the test shuts down, which eventually eats up all my disk space when running 4000+ tests (4000 * 9mb = 36GB).
This doesn't happen on Nightwatch v1.7.11, (I've just been upgrading).
npm init nightwatch
npx nightwatch ./nightwatch/examples/basic/ecosia.js
npx nightwatch ./nightwatch/examples
No response
3.5.0
20.5.1
Chrome 123.0.6312.86 (Official Build) (64-bit)
Ubuntu 20.04.6 LTS
their is no folder is getting created like /tmp/
@AbhisekOmkar are you running Ubuntu like me?
Description of the bug/issue
Hi! Here's something I've noticed:
Every time a test starts up, Chrome creates two folders under
/tmp/
:/tmp/.com.google.Chrome.PyT0E2
(empty)/tmp/.org.chromium.Chromium.OBIvvs
(aprox 9 megabytes)Though both folders are left behind when the test shuts down, which eventually eats up all my disk space when running 4000+ tests (4000 * 9mb = 36GB).
This doesn't happen on Nightwatch v1.7.11, (I've just been upgrading).
Steps to reproduce
npm init nightwatch
(from https://nightwatchjs.org/guide/quickstarts/create-and-run-a-nightwatch-test.html)/tmp/
folder.npx nightwatch ./nightwatch/examples/basic/ecosia.js
npx nightwatch ./nightwatch/examples
/tmp/
folder as Chrome creates folders and leaves them behind.Sample test
No response
Command to run
No response
Verbose Output
No response
Nightwatch Configuration
No response
Nightwatch.js Version
3.5.0
Node Version
20.5.1
Browser
Chrome 123.0.6312.86 (Official Build) (64-bit)
Operating System
Ubuntu 20.04.6 LTS
Additional Information
No response