MS Edge driver selenium error: DevToolsActivePort file doesn't exist , works

Shetty 1 Reputation point
2021-03-18T02:16:37.467+00:00

MSEdgeDriver and browser version used 88.0.705.63 (64 bit). Works when provided with edge options.addArguments("--headless"); but does not worked when this is removed. The below error is thrown
Message: org.openqa.selenium.WebDriverException: unknown error: DevToolsActivePort file doesn't exist Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: 'A036T0L6347NRVX', ip: '10.227.221.75', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_66' Driver info: driver.version: EdgeDriver remote stacktrace: Backtrace: Ordinal0 [0x00007FF6D6D0AF92+241554] GetHandleVerifier [0x00007FF6D747CA88+2173368] GetHandleVerifier [0x00007FF6D749FAC8+2316792] GetHandleVerifier [0x00007FF6D7499BC9+2292473] GetHandleVerifier [0x00007FF6D74CB760+2496144] GetHandleVerifier [0x00007FF6D74C7A5F+2480527] GetHandleVerifier [0x00007FF6D74A550A+2339898] GetHandleVerifier [0x00007FF6D74A614B+2343035] Ordinal0 [0x00007FF6D6CE2D01+77057]
Edge options used : `` EdgeOptions options = new EdgeOptions(); options.addArguments("--no-sandbox"); options.setBinary("C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"); options.addArguments("--disable-dev-shm-usage"); // overcome limited resource problems options.addArguments("disable-infobars"); // disabling infobars options.addArguments("--disable-extensions"); // disabling extensions options.addArguments("--disable-gpu"); // applicable to windows os only options.addArguments("--disable-dev-shm-usage");

Microsoft Edge
Microsoft Edge
A Microsoft cross-platform web browser that provides privacy, learning, and accessibility tools.
2,144 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yu Zhou-MSFT 12,071 Reputation points Microsoft Vendor
    2021-03-19T02:03:42.95+00:00

    Hi @Shetty

    I think the issue has been solved in your stackoverflow post :)

    Adding --remote-debugging-port=<port> as a workaround.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Regards,
    Yu Zhou

    0 comments