I'm using Chromedriver in the following way:
chrome_options = Options()
chrome_options.add_argument('--no-sandbox')
chrome_options.add_argument('--window-size=1420,1080')
chrome_options.add_argument('--headless')
chrome_options.add_argument('--disable-dev-shm-usage')
chrome_options.add_argument('--disable-gpu')
chrome_options.add_argument("--disable-notifications")
chrome_options.add_argument("--remote-debugging-port=9222")
chrome_options.add_experimental_option("excludeSwitches", ["enable-automation"])
chrome_options.add_experimental_option('useAutomationExtension', False)
chrome_options.binary_location='/usr/bin/google-chrome-stable'
chrome_driver_binary = "/usr/bin/chromedriver"
driver = webdriver.Chrome(executable_path=chrome_driver_binary, chrome_options=chrome_options)
In trying to clear some space in my ec2 instance, I'm noticing I also have the following:
-rwxr-xr-x 1 root root 197M Mar 1 20:43 /usr/lib/chromium-browser/chromium-browser
Does Chromedriver need chromium-browser as some sort of dependency, or am I OK to delete chromium-browser? It appears I only use google-chrome with Chromedriver, but again I'm not exactly sure if I need chromium-browser on the backend of things.
CodePudding user response:
chromedriver
is just interface plumbing that controls chromium-browser
, which does the real work.
CodePudding user response:
As per the documentation:
- Chromium is an open-source and free web browser that is managed by the Chromium Project.
- Google Chrome is a proprietary browser developed and managed by Google.
Unlike Chromium, Google Chrome offers built-in support for media codecs like MP3, H.264, and AAC, as well as Adobe Flash.
Conclusion
If your tests are not dependent on Chromium browser you can safely delete it.