-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snap-Chromium eating disk space #200
Comments
I should also add that in '/tmp/snap-private-tmp/snap.chromium/tmp' I have 2756 folders of 'chromedp-runner' profiles. |
I just want to add my workaround just in case anyone faces the same issue, it may not be desirable but it works: Add Before running GoWitness: mkdir "https-split" && cd "$_"
split -l 500 "../https.txt"
cd .. Then run GoWitness with: for file in https-split/*; do
gowitness file -X 2560 -Y 1440 -F -f "$file" -t 1
sudo rm -rf /tmp/snap-private-tmp/snap.chromium*
done |
Describe the bug
As Snap Chromium is used for GoWitness, it will fill up the '/tmp' directory until is has either finished or disk usage is at 100%.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Disk not the be filled up and clutter to be automatically removed.
Version Information:
Additional context
I have a list of 9190 subdomains. My tmp folder was empty, as I had just recently restarted my server. Upon checking back a day later, I noticed it had hung and when checking my disk usage, I was a 100% with 6.9GB '/tmp' folder, 6.9GB of which being '/tmp/snap-private-tmp/snap.chromium'. I checked what line the last subdomain was at, and it only made it to line 4713 before reaching 100% disk usage.
The text was updated successfully, but these errors were encountered: