Wsrtjtyk

This error message...

org.openqa.selenium.WebDriverException: unknown error: DevToolsActivePort file doesn't exist 

...implies that the ChromeDriver was unable to initiate/spawn a new WebBrowser i.e. Chrome Browser session.

Your code trials and the versioning information of all the binaries would have given us some hint about what's going wrong.

However as per Add --disable-dev-shm-usage to default launch flags seems adding the argument --disable-dev-shm-usage will temporary solve the issue.

If you desire to initiate/span a new Chrome Browser session you can use the following solution:

System.setProperty("webdriver.chrome.driver", "C:\path\to\chromedriver.exe");

ChromeOptions options = new ChromeOptions();

options.addArguments("start-maximized"); // open Browser in maximized mode

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"); // overcome limited resource problems

options.addArguments("--no-sandbox"); // Bypass OS security model

WebDriver driver = new ChromeDriver(options);

driver.get("https://google.com");

disable-dev-shm-usage

As per base_switches.cc disable-dev-shm-usage seems to be valid only on Linux OS:

#if defined(OS_LINUX) && !defined(OS_CHROMEOS)

// The /dev/shm partition is too small in certain VM environments, causing

// Chrome to fail or crash (see http://crbug.com/715363). Use this flag to

// work-around this issue (a temporary directory will always be used to create

// anonymous shared memory files).

const char kDisableDevShmUsage = "disable-dev-shm-usage";

#endif

In the discussion Add an option to use /tmp instead of /dev/shm David mentions:

I think it would depend on how are /dev/shm and /tmp mounted.
If they are both mounted as tmpfs I'm assuming there won't be any difference.
if for some reason /tmp is not mapped as tmpfs (and I think is mapped as tmpfs by default by systemd), chrome shared memory management always maps files into memory when creating an anonymous shared files, so even in that case shouldn't be much difference. I guess you could force telemetry tests with the flag enabled and see how it goes.

As for why not use by default, it was a pushed back by the shared memory team, I guess it makes sense it should be useing /dev/shm for shared memory by default.

Ultimately all this should be moving to use memfd_create, but I don't think that's going to happen any time soon, since it will require refactoring Chrome memory management significantly.

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");

I had the same problem in python. The above helped. Here is what I used in python -

chrome_options = Options()

chrome_options.add_argument('--headless')

chrome_options.add_argument('--no-sandbox')

chrome_options.add_argument('--disable-dev-shm-usage')

driver = webdriver.Chrome('/path/to/your_chrome_driver_dir/chromedriver',chrome_options=chrome_options)

We were having the same issues on our jenkins slaves (linux machine) and tried all the options above.

The only thing helped is setting the argument

chrome_options.add_argument('--headless')

But when we investigated further, noticed that XVFB screen doesn't started property and thats causing this error. After we fix XVFB screen, it resolved the issue.

I had the same issue, but in my case chrome previously was installed in user temp folder, after that was reinstalled to Program files. So any of solution provided here was not help me. But if provide path to chrome.exe all works:

chromeOptions.setBinary("C:\Program Files (x86)\Google\Chrome\Application\chrome.exe");

I hope this helps someone =)

It seems there are many possible causes for this error. In our case, the error happened because we had the following two lines in code:

System.setProperty("webdriver.chrome.driver", chromeDriverPath);

chromeOptions.setBinary(chromeDriverPath);

It's solved by removing the second line.

No solution worked for my. But here is a workaround:

maxcounter=5

for counter in range(maxcounter):

    try:           

        driver = webdriver.Chrome(chrome_options=options,

                          service_log_path=logfile,

                          service_args=["--verbose", "--log-path=%s" % logfile])

        break

    except WebDriverException as e:

        print("RETRYING INITIALIZATION OF WEBDRIVER! Error: %s" % str(e))

        time.sleep(10)

        if counter==maxcounter-1:

            raise WebDriverException("Maximum number of selenium-firefox-webdriver-retries exceeded.")

In my case it happened when I've tried to use my default user profile:

...

options.addArguments("user-data-dir=D:\MyHomeDirectory\Google\Chrome\User Data");

...

This triggered chrome to reuse processes already running in background, in such a way, that process started by chromedriver.exe was simply ended.

Resolution: kill all chrome.exe processes running in background.

In my case, I was trying to create a runnable jar on Windows OS with chrome browser and want to run the same on headless mode in unix box with CentOs on it. And I was pointing my binary to a driver that I have downloaded and packaged with my suite. For me, this issue continue to occur irrespective of adding the below:

        ChromeOptions options = new ChromeOptions();

        options.addArguments("--headless");

        options.addArguments("--no-sandbox");

        System.setProperty("webdriver.chrome.args", "--disable-logging");

        System.setProperty("webdriver.chrome.silentOutput", "true");

        options.setBinary("/pointing/downloaded/driver/path/in/automationsuite");

        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"); // overcome limited resource problems

        options.addArguments("window-size=1024,768"); // Bypass OS security model

        options.addArguments("--log-level=3"); // set log level

        options.addArguments("--silent");//

        options.setCapability("chrome.verbose", false); //disable logging

        driver = new ChromeDriver(options);

Solution that I've tried and worked for me is, download the chrome and its tools on the host VM/Unix box, install and point the binary to this in the automation suite and bingo! It works :)

Download command:
wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm

Install command:
sudo yum install -y ./google-chrome-stable_current_*.rpm

Update suite with below binary path of google-chrome:
options.setBinary("/opt/google/chrome/google-chrome");

And.. it works!

I solve this problem by installing yum -y install gtk3-devel gtk3-devel-docs", it works ok

My work env is :

Selenium Version 3.12.0

ChromeDriver Version v2.40

Chrome 68 level

Before:

After:

Since this is the most active message for this type of error, I wanted to mention my solution (after spending hours to fix this).

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)

Thanks everybody for your comments that make me understand and resolve the issue.