-
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
driver.quit not working #1667
Comments
same |
Same here |
same |
I have created a custom function that is run at __del of my class. This is for my specific case where I have a specific browser folder I use / set in the class that uses ChromeDriver, and can probably be implemented in more general way. self.user_data_folder is set like this in the beginning of my code where i instantiate the chrome with this options : chrome_options.add_argument(f"--user-data-dir={self.user_data_folder}")
|
Made this workaround which has been bulletproof enough to run in a loop for a couple days with no issues, similar to @typhoon93's approach. I'm not skilled enough to add this to uc's init and PR but I'm sure it's possible. Apparently the quit() is "crashing" the driver and the crashpad process lingers(?), same goes for the renderer
|
Same, crashes when used headless with persistent session, not crashes when non headless with persistent session |
Thanks for the workaround. |
The short term fix in this issue for me was addressing the error line:
without this, the code was reaching 'break' and trying to perform actions continuously. |
driver.quit closes the driver window but leaves the chromes in task manager which eat the CPU
The text was updated successfully, but these errors were encountered: