我试图用一个URL启动chrome浏览器，浏览器启动后，它什么也不做。
1分钟后我看到如下错误:
Unable to open browser with url: 'https://www.google.com' (Root cause: org.openqa.selenium.WebDriverException: unknown error: DevToolsActivePort file doesn't exist
(Driver info: chromedriver=2.39.562718 (9a2698cba08cf5a471a29d30c8b3e12becabb0e9),platform=Windows NT 10.0.15063 x86_64) (WARNING: The server did not provide any stacktrace information)
我的配置:
Chrome浏览器:66 ChromeBrowser: 2.39.56
又及，在Firefox中一切都很好
当前回答
我使用铬，但我已经创建了一个shell脚本称为铬，只是为了便于我从dmenu打开浏览器。
#!/bin/bash
/usr/bin/chromium
Chrome驱动程序在PATH中寻找Chrome并执行。结果我得到了同样的错误。
org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited normally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /home/s1n7ax/.local/share/s1n7ax/bin/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 's1n7ax', ip: '127.0.1.16', os.name: 'Linux', os.arch: 'amd64', os.version: '5.4.70-1-lts', java.version: '11.0.8'
Driver info: driver.version: ChromeDriver
remote stacktrace: #0 0x56030c96dd99 <unknown>
我只是删除了shell脚本，并添加了一个到chromium的软链接。现在一切正常。
其他回答
由于这是针对这类错误的最活跃的消息，所以我想提一下我的解决方案(在花了几个小时来修复这个问题之后)。
On Ubuntu 18.04, using Chrome 70 and Chromedriver 2.44, and Python3 I kept getting the same DevToolsActivePort error, even when I disabled all options listed above. The chromedriver log file as well as ps showed that the chromedriver I set in chrome_options.binary_location was running, but it always gave DevToolsActivePort error. When I removed chrome_options.binary_location='....' and add it to webdriver creation, I get it working fine. webdriver.Chrome('/path to ... /chromedriver',chrome_options=chrome_options)
感谢大家的意见，让我理解并解决了这个问题。
I started seeing this problem on Monday 2018-06-04. Our tests run each weekday. It appears that the only thing that changed was the google-chrome version (which had been updated to current) JVM and Selenium were recent versions on Linux box ( Java 1.8.0_151, selenium 3.12.0, google-chrome 67.0.3396.62, and xvfb-run). Specifically adding the arguments "--no-sandbox" and "--disable-dev-shm-usage" stopped the error. I'll look into these issues to find more info about the effect, and other questions as in what triggered google-chrome to update.
ChromeOptions options = new ChromeOptions();
...
options.addArguments("--no-sandbox");
options.addArguments("--disable-dev-shm-usage");
我在与jenkins服务器集成时也遇到了这个问题，我使用了jenkin工作的根用户，当我将用户更改为其他用户时，这个问题得到了解决。我不确定为什么根用户会出现这个错误。
谷歌Chrome浏览器版本71.0 ChromeDriver版本2.45 CentOS7版本1.153
当chromedriver无法找出chrome正在使用的调试端口时，就会发生这种情况。
一个可能的原因是HKEY_CURRENT_USER\Software\Policies\谷歌\Chrome\UserDataDir的开放缺陷
但在我的最后一个病例中，是其他一些不明原因。
幸运的是，手动设置端口号:
final String[] args = { "--remote-debugging-port=9222" };
options.addArguments(args);
WebDriver driver = new ChromeDriver(options);
如果添加参数/选项不能解决问题，那么可能是/tmp目录的权限问题。
确保执行Chrome的用户有权限在/tmp文件夹下创建文件夹/files。这就是我案例中的解
