selenium-google-code-issue-archive icon indicating copy to clipboard operation
selenium-google-code-issue-archive copied to clipboard

If Firefox process failed to start, FirefoxDriver enters the endless loop waiting for it to start

Open lukeis opened this issue 8 years ago • 6 comments

Originally reported on Google Code with ID 7609

I have noticed the following:

* Supposing firefox binary when launched, crashes immediately (e.g. missing symbols).
* FirefoxDriver calls stopClient(), which after few intermediate functions, calls CommandLine.destroy(),
which calls UnixProcess.destroy() which in first place calls watchdog.waitForProcessStarted().
And that causes looping forever waiting for process to start, while it has already
finished.

I think correct code for CommandLine.destroy() should be:

public int destroy() {
  if (isRunning()) {
    return process.destroy();
  }
}

Reported by Dmitry.Katsubo on 2014-07-15 15:24:09

lukeis avatar Mar 04 '16 08:03 lukeis

Reported by barancev on 2014-07-15 19:59:28

  • Labels added: Lang-Java

lukeis avatar Mar 04 '16 08:03 lukeis

I believe I may running into this issue as well, but want to confirm.

Reproducible with FF 30, 31. Java Versions 7.0.45, 7.0.60, 7.0.65, Selenium v2.41,
v2.42.2

The node (running on Windows 7) console displays the following output when this occurs:


17:14:37.844 INFO - Executing: [delete session: aba691dd-42d0-4dc3-af6b-37ecdba6
ecc9] at URL: /session/aba691dd-42d0-4dc3-af6b-37ecdba6ecc9)
17:14:39.938 INFO - Command failed to close cleanly. Destroying forcefully (v2).
 org.openqa.selenium.os.UnixProcess$SeleniumWatchDog@19fa7c4

At which point an alert window will display on the VM. I have to manually close the
alert window for the browser session to be usable again. 





Reported by c.p.kelley on 2014-07-28 17:32:36

lukeis avatar Mar 04 '16 08:03 lukeis

I did some additional testing around this and found that its only reproducible with
FF 30+. I converted all my windows VMs to v29 and no longer get the error message.

Reported by c.p.kelley on 2014-07-28 19:54:05

lukeis avatar Mar 04 '16 08:03 lukeis

Well, the issue I am referring to does not depend on FF version. It can happen with
any FF version. The problem is that destroy() method requires that process is running,
however it could have already died.

Reported by Dmitry.Katsubo on 2014-07-29 17:36:27

lukeis avatar Mar 04 '16 08:03 lukeis

Hi Dmitry, I created a separate issue: 7675. If you believe my issue is unrelated I
will let me know and I will delete my comments. 

Reported by c.p.kelley on 2014-07-29 19:27:59

lukeis avatar Mar 04 '16 08:03 lukeis

Reported by luke.semerau on 2015-09-17 17:47:03

  • Labels added: Restrict-AddIssueComment-Commit

lukeis avatar Mar 04 '16 08:03 lukeis