Hello, thanks for the amazing project! When running the SeleniumBase Docker image, I noticed that the tests don't clean up the .com.google.Chrome.* directories that Chrome creates in /tmp. I would expect these files to be cleaned up as for long running containers, this could pose a potential issue in disk space (and is just unnecessary to have lying around).

Steps to reproduce:

1. Clone the master branch of this repository
2. Build the Docker image: docker build -t seleniumbase .
3. Run the Docker container interactively: docker run --rm -it seleniumbase:latest
4. Run tests: ./run_docker_test_in_chrome.sh
5. Observe the extra .com.google.Chrome.* directory left in /tmp

When I ran all tests, I had 161 extra of these directories lying around:

root@59b2a6307ab8:/# ls -a /tmp | grep com.google.Chrome | wc -l
161

Alternatives

I could just, after running a set of tests or quitting the webdriver, run a function that cleans up these directores. However, I think a native solution in SeleniumBase would be nice.