-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Description
What happened?
run this code


2025-02-09 13:31:28 -> 1739079088.0
chromdriver.log start with [1739079187.0]
which means it took exactly 99s to start webdriver.Chrome() and matched the log that i printed.
After I added 'chrome_options.add_argument("--proxy-connection-timeout=20")', got this log, stuck issues got prevented.

looks like there's an issues about set-proxy-server-timeout (which was "socks5://127.0.0.1:7890" or โhttp://127.0.0.1:7890" supported by mixed-port-clash)
However, i still got stuck issue even after i removed "--proxy-server".
I have no idea what happened.
By the way, this is a small probability event.
How can we reproduce the issue?
selenium 4.28.1
ChromeDriver 132.0.6834.159
Google Chrome 132.0.6834.159
Clash v1.17.0
Python 3.10.12
Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-94-generic x86_64)
happened randomlyRelevant log output
NoneOperating System
Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-94-generic x86_64)
Selenium version
selenium 4.28.1
What are the browser(s) and version(s) where you see this issue?
Google Chrome 132.0.6834.159
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 132.0.6834.159
Are you using Selenium Grid?
idk, just pip install Selenium