Edge Driver connection dissappears on 16281 build after several seconds

Not reproducible Issue #13640234


Pascal B.
Sep 8, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

After about 5,5 seconds (on my system), the connection to an Edge browser from Selenium 3.5.3 disappears without further information, browser closes unexpectedly.

Edge Version: 41.16281.1000.0
Microsoft WebDriver Version 10.0.16281.1000
Selenium 3.5.3 (Java Bindings)

Code to reproduce:

System.setProperty("webdriver.edge.driver","C:\\Program Files (x86)\\Microsoft Web Driver\\MicrosoftWebDriver.exe");
EdgeOptions options = new EdgeOptions();
EdgeDriver driver = new EdgeDriver(options);
System.out.println("Loading website");
System.out.println("Done Loading website");

double i = 0;
int step = 100;
long next = System.currentTimeMillis();
while(true) {
    // doing something to check if the driver still exists:
    String url = driver.getCurrentUrl();
    System.out.format("Driver still there after %.1f seconds (showing %s)\n",i/1000,url);

Expected output:
The terminal should print the url without breaking.

Actual Output:
The program stops with output:

Driver still there after 5,3 seconds (showing http://www.example.com/)
Driver still there after 5,4 seconds (showing http://www.example.com/)
org.openqa.selenium.WebDriverException: Unknown error (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:54:15.039Z'
System info: host: 'W10T3', ip: '', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_144'
Driver info: org.openqa.selenium.edge.EdgeDriver
Capabilities [{applicationCacheEnabled=true, InPrivate=false, pageLoadStrategy=normal, platform=XP, acceptSslCerts=true, browserVersion=41.16281.1000.0, platformVersion=10, locationContextEnabled=true, webStorageEnabled=true, browserName=MicrosoftEdge, takesScreenshot=true, takesElementScreenshot=true, javascriptEnabled=true, platformName=XP}]


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Status to “Not reproducible”

    • This seems to have been on a fairly old insider build, please reactivate if you’re still seeing this issue.

    • Changed Status from “Not reproducible”

    • After it has been fixed in the last months, the issue is back on the current 17074 Windows build (Using Selenium bindings 3.8.1, MSWebdriver version 10.0.17074.1000, Edge version 42.17074.1002.0).

      And again more or less 5,5 sec (give or take 100ms).

      Can be reproduced using the same code as in the issue above.

    • Microsoft Edge Team

      Changed Assigned To to “John J.”

      Changed Assigned To to “John J.”

      Changed Status to “Fixed”

      Changed Assigned To to “James M.”

      Changed Assigned To from “James M.” to “John J.”

      Changed Status from “Fixed”

      Changed Assigned To from “John J.” to “Mustapha J.”

      Changed Assigned To from “Mustapha J.” to “Clay M.”

      Changed Status to “Not reproducible”

    • Hey Pascal, we’re not able to reproduce the issue using the latest Java binding and MicrosoftWebDriver (internal builds so somewhat equivalent to the Insider fast ring). Can you please reactivate if you hit this issue again with any more details.

    You need to sign in to your Microsoft account to add a comment.

    Sign in