-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
options.add_argument("--disable-gpu") potentially fixes zombie processes not being closed properly. #1723
Comments
I have the same problem and after trying what you mentioned, the problem is still there. I don't know what to do anymore... I've even tried use_subprocess=False and it doesn't solve either.
|
@FRIKIdelTO |
I just tried it now and the problem is still there |
It solved on my end too, I was using this nuclear option will try for a couple days to see if it's a long-term solution |
Finally solved with this function (copy/paste and modified from seleniumbase):
|
I just want to say this is the ONLY solution that worked. Everyone here is talking about just killing the process while the problem is clearly a file lock which prevents the defunct process from being killed. So check your file descriptors folks. Can we get this patched ? |
The only way I fixed this issue was calling
|
A lot of people including me had a problem with chrome processes not being closed correctly sometimes.
I found out that adding
options.add_argument("--disable-gpu")
fixes it.I don't really know what to do with that because I am not an expert but I just spent all day looking for answers and that fixed it for me.
Hope that could help somebody.
The text was updated successfully, but these errors were encountered: