Open AlexanderArendar opened 7 years ago
whimboo
commented
7 years ago @whimboo The message I have mentioned in the above comment. Also the FF browser gets close before completing the script execution.
@VikasSalunke which script execution? I only see a call to get and close. Whereby the latter will shutdown Firefox because it's the last window you are closing. If you don't want that just remove the call to close.
Thesykan
commented
7 years ago I've been able to work around this issue by closing tabs before quitting out the main tab. Also setting the URL to about:config/blank before closing,
while (this.WindowHandles.Count > 1)
{
this.Navigate().GoToUrl("about:config");
this.Navigate().GoToUrl("about:blank");
this.Close(); //Close Tab
this.SwitchTo().Window(this.WindowHandles.Last());
}
this.Navigate().GoToUrl("about:config");
this.Navigate().GoToUrl("about:blank");
this.Quit(); //Then main windowHope this helps!!
Lewiscowles1986
commented
6 years ago I'm getting this on firefox nightly
I am running it in docker, could that be why? I've sent them a crash report, it's obviously a shared component
whimboo
commented
6 years ago @Lewiscowles1986 can you make sure that you set the values as proposed via https://github.com/SeleniumHQ/docker-selenium/pull/485?
Lewiscowles1986
commented
6 years ago docker run --rm -d -e DISPLAY=unix$DISPLAY -e USER_ID=$UID -e GROUP_ID=$UID -v $HOME/Downloads:/data/Downloads -v $HOME/.config/mozilla/firefox-$version:/data/.firefox -v /dev/snd:/dev/snd --privileged -v /tmp/.X11-unix:/tmp/.X11-unix --memory 1024mb --name firefox-nightly --shm-size 2g --net host firefox-nightlySeems to work nicely to stop crashes. I wish I understood why, but for now I'll be grateful
whimboo
commented
6 years ago Great. For details see https://bugzilla.mozilla.org/show_bug.cgi?id=1338771#c10.
Is anyone else here who sees this behavior and is not using Selenium in a docker? If yes, please test again with a latest Firefox Nightly build, and attach the trace log.
whimboo
commented
6 years ago After a bit of investigation in the last week, I think that this issue is related to bug 1403923 which I filed a week ago. Lets wait for a fix, and we could check the status again afterward.
namedgraph
commented
6 years ago @whimboo for me setting either -v /dev/shm:/dev/shm or --shm-size 2g did not address the problem on selenium/node-firefox:3.8.1-erbium. but the driver.get("about:config"); workaround seems to work.
whimboo
commented
6 years ago @pumba-lt then you most likely hit another issue. But that is hard to say without seeing any logs. Best you file a separate issue so we can investigate.
anto-ac
commented
6 years ago I am still getting this issue with either /dev/shm:/dev/shm or shm-size 2g in my docker compose file.
whimboo
commented
6 years ago @anto-wahanda how can you be sure about it? We would need a trace log to be able to say if that is really the underlying issue.
anto-ac
commented
6 years ago @whimboo I tried using either options (not together) and I ended up with timeouts as described in this and other issues. I will try to get a trace log together, but it’s not always easy because it doesn’t happen consistently and it is subject to some kind of Schroedingers’s cat effect :)
My OS properties:
In 'About Mozilla Firefox' info I can see this:
I have Selenium WebDriver java 3.0.0. Gecko driver version is geckodriver-v0.11.1-linux64.tar.gz
When I run a simple ScalaTest test suite with 1 test which calls the driver.close in the end there's nothing happening, the test reports as passed but the Firefox window is not closed. Here is a full output from the console:
Note that last 4 lines in the output before the final line is the output of the test.