Selenium Webdriver Error regarding destroyHarder

Question

What a mistake below. This happens when I execute the webdriver script in eclipse:

June 20, 2014 1:20:54 pm org.openqa.selenium.os.UnixProcess $ SeleniumWatchDog destroyHarder INFO: The command could not completely close. Strong destruction (v2). org.openqa.selenium.os.UnixProcess$SeleniumWatchDog@118ed3c

Answer 1

This is mistake. I think you need to downgrade your firefox to 29 if you are using firefox 30.

Please find the URL below for more details.

https://code.google.com/p/selenium/issues/detail?id=7506

Answer 2

I ran into this problem in one of four test projects.

Initial research led me to conclude that this happens when I try to exit Firefox while the page is still loading (green circle on the tab)

If you use Java, you can try the following:

ExpectedCondition<Boolean> pageLoadFinishedCondition = new ExpectedCondition<Boolean>() { public Boolean apply(WebDriver driver) { return ((JavascriptExecutor) driver).executeScript( "return document.readyState").equals("complete"); } }; WebDriverWait wait = new WebDriverWait(driver, 30); wait.until(pageLoadFinishedCondition); 

UPD:

But keep in mind that the “document ready” event occurs a little earlier than firefox stops this green circle, so you may need a little downtime.

Further research has shown that this is highly dependent on the application itself (and in my case it did not work). when I was on the application login page, I could not exit while on the toolbar, everything was in order.

I suggest you try the following:

• Switching to Firefox <30 (problem persists at 33)
• Close while on another page of the application (come up with a stub here)
• Do driver.navigate().refresh(); or something like that.
• Giant idle before quit () sometimes helps, say 2 * implicitlywait

UPD:

5. In addition, removing the plugin-container.exe file may help. Please note that after I deleted one, flash no longer loaded on my page.

Answer 3

I am also facing the same problem since I upgraded to Firefox. This seems like a compatibility bug with the Firefox plugin. I'm not sure if this drop will help.

But I removed driver.quit (); from my code, since I did not want the browser to close even after the script was executed. This stopped the errors.

Answer 4

Add a try catch block to the test annotation.

 try { Thread.sleep(2000); } catch (InterruptedException e) { e.printStackTrace(); } 

or you can try it too

 try{ driver.close(); } } catch (InterruptedException e) { e.printStackTrace(); } 

in after annotation.

He must solve the problem.

Answer 5

instead of simple

 driver.quit(); 

using:

 driver.close(); try { Thread.sleep(5000); driver.quit(); } catch (Exception e) { } 

Answer 6

This works for me, interesting. But this applies to the case when you open only one browser, when close () matches quit ().

  driver.close(); try { Thread.sleep(1000); //driver.quit(); } catch (Exception e) { }