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

Firefox profiles with RemoteWebDriver #3046

Closed
martmo opened this issue Nov 2, 2016 · 7 comments
Closed

Firefox profiles with RemoteWebDriver #3046

martmo opened this issue Nov 2, 2016 · 7 comments

Comments

@martmo
Copy link

martmo commented Nov 2, 2016

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?

@lukeis
Copy link
Member

lukeis commented Nov 2, 2016

this should have been fixed in 3.0.1 related issue #2914

@martmo
Copy link
Author

martmo commented Nov 3, 2016

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

@bradhasha
Copy link

bradhasha commented Feb 13, 2017

@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.

@mart44
Copy link

mart44 commented Feb 14, 2017

@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

@bradhasha
Copy link

Thank you @mart44. I'll probably do the same until this issue is resolved.

@m7stock
Copy link

m7stock commented Apr 28, 2017

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).

find /tmp/*webdriver-profile -maxdepth 0 -type d -mmin +60 -exec rm -rf "{}" \;

@diemol
Copy link
Member

diemol commented Sep 23, 2018

Duplicate of #5209

(and fixed via 0bea0a1)

@diemol diemol closed this as completed Sep 23, 2018
@lock lock bot locked and limited conversation to collaborators Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants