69.0.3497.100 (Official Build) (64-bit) not running protractor tests, but gives errors

[aldo...@gmail.com]

Hi all,

Until a few weeks ago I used to have my Protractor e2e test working with th Chrome browser. However since the Chrome update 69.0.3497.100 (Official Build) (64-bit) I just tried to run chrome in a non headless mode (as if in chromeOptions in the config file I add "--headless") all works fine. But if I remove it to have a test with the chrome browser with protractor, while Chrome loads and shows a tab withe the address of data;, I get this error message in the command prompt:

WebDriverError: unknown error: Chrome failed to start: crashed
(unknown error: DevToolsActivePort file doesn't exist)
(Driver info: chromedriver=2.41.578737......)

If this gives any help, if the test is run via the Firefox browser all works the pages change, and the broswer is closed when the tests complete.

I've through various dicussion tops and did a webdriver-manager clean and after a webdriver-manager update.
I also manually install chromedriver@latest via npm but still no luck.

Can anyone help please?

[John Chen]

Hi,

Do you happen to have --user-data-dir option in your config file? This sounds like what happens when two instances of Chrome try to use the same user data directory. It might worth trying to remove that option if you're using it.

another thing to try is to close all your Chrome windows and stop all Chrome processes before running the test.

Hope that helps.

John

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[aldo...@gmail.com]

Hi John,

Thanks for the answer, but I always close Chrome before I run the tests using the chrome in non-headsless mode. This is because I experienced that issue in the past and I learnt to close all open instances of the browser of the type protractor will test with before I run protractor.

In the config file, I didn't have the --user-data-dir argument set. I had the following:
chromeOptions: {
args: ["--disable-gpu", "--no-sandbox", '--disable-web-security']
}

After I added that argument, the tests still don't run, but at the browser no longer stops withan empty new tab with data; in the address bar but loads well and 'data;' text is cleared from the new browser tab address bar and the default display when a new tab is shown Chrome shows when the browser is opened nomally.

In my previous post, and noticed today is that at the very end of the error text in the command prompt, there is the line:
E/launcher - Process exited with error code 199
before which there are many lines saying:
[19348:19608:0920/111806.783:ERROR:in_progress_cache_impl.cc(192)] Cache is not initialized, cannot RetrieveEntry.