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

Throws org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died. #3026

Closed
akuzmenkovs opened this issue Oct 28, 2016 · 1 comment

Comments

@akuzmenkovs
Copy link

Meta -

OS: Windows Server 2008 R2
Selenium Version:
Selenium-standalone 3.0.0
Browser:
Google Chrome
Browser Version:
v53.0.2785.116

Expected Behavior -

Should throw NoSuchElementException or even found elements(it worked sometimes for me)

Actual Behavior -

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.
Build info: version: '3.0.0', revision: '350cf60', time: '2016-10-13 10:48:57 -0700'
os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_45'
Driver info: driver.version: RemoteWebDriver

Steps to reproduce -

Could reproduce it if search for element like:
button[data-id=something];
li[data-original-index=something];

Probably because it doesn't include ordinary quotes, cause this button[data-id='something']; format works and founds elements as it should.

Backtrace

at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:622) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:368) at org.openqa.selenium.remote.RemoteWebDriver.findElementByCssSelector(RemoteWebDriver.java:465) at org.openqa.selenium.By$ByCssSelector.findElement(By.java:430) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:360)

@lukeis
Copy link
Member

lukeis commented Oct 28, 2016

Please provide a completely reproducible test case for us that would include a link to a page or html (including css / javascript) along with a WebDriver script to reproduce the issue. Without this there is little to nothing one can do to help with your issue. Please do not expect others volunteering their time to work at reproducing your issue.

When a reproducible test case is provided we can reopen the issue.

@lukeis lukeis closed this as completed Oct 28, 2016
@lock lock bot locked and limited conversation to collaborators Aug 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants