Unfortunately, when we open more than one thread of undetected chromedriver, if we quit one, the others will be closed.

[boludoz]

Unfortunately, when we open more than one thread of undetected chromedriver, if we use driver.quit(), the others will be closed.

[boludoz]

In theory the problem should be in the way it closes, possibly the taskill.

[mdmintz]

Duplicate of #2006 (comment)

Only pytest multithreading is supported via pytest-xdist.

In the pytest Syntax Formats, the driver is automatically quit at the end of each test. Therefore, if you were calling driver.quit() manually, then you probably weren't using UC Mode with pytest.

[boludoz]

Duplicate of #2006 (comment)

Only pytest multithreading is supported via pytest-xdist.

In the pytest Syntax Formats, the driver is automatically quit at the end of each test. Therefore, if you were calling driver.quit() manually, then you probably weren't using UC Mode with pytest.

I only need to take data from a protected web and write them down on one without any protection. When using without UC it works correctly. It seems to be a UC-only bug.

[boludoz]

Disabling:

    "uc_subprocess": False,
    "uc_cdp_events": False

Works in UC mode, I guess it will be the same as nothing. Maybe placing the custom chromedriver route will work.