Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with undetected_chromedriver #590

Open
robertszooba opened this issue May 11, 2024 · 1 comment
Open

Problem with undetected_chromedriver #590

robertszooba opened this issue May 11, 2024 · 1 comment

Comments

@robertszooba
Copy link

The problem I often face (besides #589) is undetected_chromedriver, more specifically:

selenium.common.exceptions.WebDriverException: Message: unknown error: cannot connect to chrome at 127.0.0.1:61315
from chrome not reachable
Stacktrace:
0   undetected_chromedriver             0x0000000107755ae8 undetected_chromedriver + 5217000
[...]
19  libsystem_pthread.dylib             0x00007ff804eb0ae3 thread_start + 15

[2024/05/11 16:00:22|__init__.py             |INFO    ]: ensuring close

Interestingly, sometimes the program does start. It's as if the driver search is happening in a non-deterministic manner, which seems improbable.

Is it a known way to fix this problem?

@codders
Copy link

codders commented May 12, 2024

I think this message means that the browser process has died. This can happen after a while - maybe there's a memory leak somewhere. You can try increase the memory available (if you're running inside docker, for example, with limited memory available). Alternatively, you can run flathunter in 'one-shot' mode - turn off loop, and just trigger periodic runs out of cron so that you're always getting a fresh process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants