sebdelsol
sebdelsol
But it's only needed on Windows. On Posix multiprocessing forks instead of spawning another interpreter. Anyway it's always good practice to protect your main entry point. Besides the error message...
If you manually interrupt your script how the code to quit the driver and close the browser would be executed ?
you properly quit your drivers
If you interrupt your script then you'll end up with a lot of **chromedrivers** and **temp profile folders**. You have either to `driver.quit()` or let your script finish to trigger...
Please try my [**fork**](https://github.com/sebdelsol/undetected-chromedriver) where I fixed the Preferences merge bug . `pip install git+https://github.com/sebdelsol/undetected-chromedriver@master`
Which bugs prevent you from upgrading ?
You could try to use 102 (103 has a nagging issue #694) with [seleniumwire](https://pypi.org/project/selenium-wire/) for proxies with authentication. Maybe there's something wrong in your multi-thread code, do you have minimal...
Please check this [**answer**](https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/536#issuecomment-1061772136) for how to use seleniumwire. There are indeed some [**caveats**](https://github.com/wkeeling/selenium-wire/issues/427#issuecomment-950289962) for using seleniumwire.
You don't need to install the driver anymore, please read the doc. EDIT: * You should use undected_chromedriver `options` instead of Selenium ones. * Only `"prefs"` experimental options are working....