What happened?
I'm using the browser leftovers cleanup feature with Chrome container by setting SE_ENABLE_BROWSER_LEFTOVERS_CLEANUP=true.
However, I still find the disk filling up over weeks because of directories like these ones.
drwx------ 2 seluser seluser 4096 Mar 12 01:03 .org.chromium.Chromium.scoped_dir.0Uf94O
drwx------ 35 seluser seluser 4096 Mar 19 03:37 .org.chromium.Chromium.scoped_dir.0xg6td
drwx------ 2 seluser seluser 4096 Mar 21 01:29 .org.chromium.Chromium.scoped_dir.19ceBm
drwx------ 35 seluser seluser 4096 Apr 9 15:49 .org.chromium.Chromium.scoped_dir.4e0KOC
drwx------ 35 seluser seluser 4096 Mar 22 03:32 .org.chromium.Chromium.scoped_dir.6Ymb2K
I kept the default SE_BROWSER_LEFTOVERS_TEMPFILES_DAYS of 1 day, so they should have been long deleted.
The problems seems fairly simple: the chrome-cleanup.sh script is just looking for ".com.google.Chrome.*" and not for ".org.chromium.Chromium..*".
Command used to start Selenium Grid with Docker (or Kubernetes)
services:
hub:
image: selenium/hub:4.38.0-20251025
mem_limit: 1g
ports:
- "${HUB_PORT}:4444"
environment:
- SE_SESSION_REQUEST_TIMEOUT=600
- SE_JAVA_OPTS=-Xmx${HUB_MX} -XX:MaxMetaspaceSize=${HUB_MAX_METASPACE}
- SE_ENABLE_TRACING=false
chrome:
depends_on:
- hub
shm_size: 2gb
mem_limit: 1.2g
image: selenium/node-chrome:4.38.0-20251025
ports:
- "${CHROME_NOVNC_PORT_RANGE}:7900"
environment:
- SE_EVENT_BUS_HOST=hub
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- SE_ENABLE_BROWSER_LEFTOVERS_CLEANUP=true
- SE_VNC_NO_PASSWORD=1
- SE_JAVA_OPTS=-Xmx${NODE_MX} -XX:MaxMetaspaceSize=${NODE_MAX_METASPACE}
- TZ=${NODE_TIMEZONE}
- SE_ENABLE_TRACING=false
deploy:
replicas: ${CHROME_REPLICAS}Relevant log output
The cleanup script output is apparently lost, but the script seems to be running (ps aux reports it) and other directories are being cleaned.
Operating System
Ubuntu 24
Docker Selenium version (image tag)
4.38.0-20251025
Selenium Grid chart version (chart version)
No response
What happened?
I'm using the browser leftovers cleanup feature with Chrome container by setting
SE_ENABLE_BROWSER_LEFTOVERS_CLEANUP=true.However, I still find the disk filling up over weeks because of directories like these ones.
I kept the default
SE_BROWSER_LEFTOVERS_TEMPFILES_DAYSof 1 day, so they should have been long deleted.The problems seems fairly simple: the
chrome-cleanup.shscript is just looking for".com.google.Chrome.*"and not for".org.chromium.Chromium..*".Command used to start Selenium Grid with Docker (or Kubernetes)
services: hub: image: selenium/hub:4.38.0-20251025 mem_limit: 1g ports: - "${HUB_PORT}:4444" environment: - SE_SESSION_REQUEST_TIMEOUT=600 - SE_JAVA_OPTS=-Xmx${HUB_MX} -XX:MaxMetaspaceSize=${HUB_MAX_METASPACE} - SE_ENABLE_TRACING=false chrome: depends_on: - hub shm_size: 2gb mem_limit: 1.2g image: selenium/node-chrome:4.38.0-20251025 ports: - "${CHROME_NOVNC_PORT_RANGE}:7900" environment: - SE_EVENT_BUS_HOST=hub - SE_EVENT_BUS_PUBLISH_PORT=4442 - SE_EVENT_BUS_SUBSCRIBE_PORT=4443 - SE_ENABLE_BROWSER_LEFTOVERS_CLEANUP=true - SE_VNC_NO_PASSWORD=1 - SE_JAVA_OPTS=-Xmx${NODE_MX} -XX:MaxMetaspaceSize=${NODE_MAX_METASPACE} - TZ=${NODE_TIMEZONE} - SE_ENABLE_TRACING=false deploy: replicas: ${CHROME_REPLICAS}Relevant log output
Operating System
Ubuntu 24
Docker Selenium version (image tag)
4.38.0-20251025
Selenium Grid chart version (chart version)
No response