Update __init__.py

[Mister-Stein]

Delete the line that breaks the ability to choose whether to use Chrome's "--no-sandbox" argument or not. That functionality is already, and supposed to be achieved through "no_sandbox" argument in the "init" method of the UC's Chrome class.
It may solve these issues: #1507 #1445 #1270
@ultrafunkamsterdam you should apply this commit as soon as possible, so people can use UC on Windows safely.

[Mister-Stein]

Many people are frustrated by the common issue on Windows: UC is eating up all the resources because of zombie/dangling chrome.exe processes, that appear after invoking driver.quit() method. I was researching pretty long to find the solution, and I found it. The root cause is Chrome's --no-sandbox argument. It's appliance controlled through no_sandbox argument of uc.Chrome class. no_sandbox is set to True by default, because most of the times UC doesn't work on Linux without --no-sandbox Chrome argument(when running test script as root user for example). We should set no_sandbox to False, and no zombie processes will remain after driver.quit():

uc.Chrome(driver_executable_path=driver_executable_path, options=options, user_data_dir=user_data_dir, no_sandbox=False, user_multi_procs=True, use_subprocess=False)

Users say that undetected-chromedriver doesn't work without --no-sandbox Chrome argument on Windows 7 and lower, but works on Windows 8.1 and above. I didn't tested that for myself, but I think it's true.
Concluding all that information, set no_sandbox argument of uc.Chrome to False for Windows, and set to True for Linux.
But even more, undetected-chromedriver has breached no_sandbox functionality, so --no-sandbox is always set, whether or not you set it to True or False. This PR is fixing that issue, and people should know to use --no-sandbox with extreme caution on Windows.
This is why users report that when they used Selenium everything was fine, but when they switched to UC everything is crashed. That happens because of the breached no_sandbox functionality in UC. Selenium doesn't apply --no-sandbox by default obviously, but UC does.

[STRATZ-Ken]

I am on Windows 10, and I can confirm setting this to True or False will not help with the driver.quit() or driver.close(). At this point I am just taskkill chome on my pc every 10 minutes.

[yuryprogl]

it helps, no_sandbox=False i used. And dont use driver.quit() or driver.close(), it will automatically quit