-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Firefox profiles with RemoteWebDriver #3046
Comments
this should have been fixed in 3.0.1 related issue #2914 |
Definitely still an issue, our C# code is identical to that we were running on Selenium 2.53.1 plus we are calling RemoteWebDriver.Quit() to initiate cleanup |
@lukeis This is still an issue for me as well. My temp directory on my selenium grid server is becoming full fairly quickly. I am calling driver.quit(), but the temporary profiles do not get deleted. I am using Selenium Java. |
@bradhasha in the end we reverted back to 2.53.1 as we were unable to resolve the issue with profiles not being cleaned up |
Thank you @mart44. I'll probably do the same until this issue is resolved. |
As a workaround, you can delete old profiles by a cron or similar scheduled task until this issue is fixed (occurs on CentOS 6.8 also).
|
Meta -
OS:
Windows Server 2-12 R2
Selenium Version:
3.0.1
Browser:
Firefox 47.0.1
Browser Version:
47.0.1
Expected Behavior -
When running tests from .Net client all is well, tests run as expected. Once tests are completed, the firefox profiles generated on the target Grid nodes in temp directories should be deleted.
Actual Behavior -
The firefox profiles generated in C:\users<username>\AppData\Local\Temp\ with name anonymouswebdriver-profile are not deleted once the tests complete. Each one of these dir are ~4 MB which very quickly adds up to considerable space. When running under 2.53.1 this did not occur, is this a reoccurrence of an earlier bug?
The text was updated successfully, but these errors were encountered: