While browsing I am using cisco-cloud-web-security extension

Last successfully worked google-chrome-beta version: 60.0.3112.78
Failure started with google-chrome-beta version: 61.0.3163.31

Since this is Chromedriver related bug tagging it with "Tests>WebDriver" for further triage

23karishma@,

- How often do you see this issue?
- Can you please try executing the test with the latest Chromedriver v2.31. It can be downloaded from https://sites.google.com/a/chromium.org/chromedriver/downloads .
- Do you see any issue on launching Chrome manually without Chromedriver?
- please provide chromedriver verbose log

Hi,

With google chrome beta 61.0.3163.31 onwards, I am always seeing this issue. I have tried  Chromedriver v2.31 and  Chromedriver v2.30 and in both cases issue persist.

Note: Everything works fine if i will use  google-chrome-beta version: 60.0.3112.78

Thanks,
Karishma

Thank you for providing more feedback. Adding requester "gmanikpure@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

23karishma@, could you please answer to the below questions from comment#5?

- Do you see any issue on launching Chrome manually without Chromedriver?
- please provide chromedriver verbose log

Also, can you please launch Chrome manually from terminal in below two ways and let us know how it goes?

1) "/opt/google/chrome-beta/google-chrome-beta" --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --disable-web-resources --enable-automation --enable-logging --force-fieldtrials=SiteIsolationExtensions/Control --ignore-certificate-errors --log-level=0 --metrics-recording-only --no-first-run --password-store=basic --remote-debugging-port=12078 --safebrowsing-disable-auto-update --test-type=webdriver --use-mock-keychain --user-data-dir="/usr/local/<username>/Downloads/profile" data:,

2) "/opt/google/chrome-beta/google-chrome-beta"

Hello,

I am not seeing any issue on launching Chrome manually without Chromedriver.

I am using selenium-stanalone-server 2.53.1. Can that be an issue ?
Can you help me to get chromedriver verbose log?

Thanks,
Karishma

Thank you for providing more feedback. Adding requester "gmanikpure@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

re comment#9, you can find information on how to enable versbose logging here : https://sites.google.com/a/chromium.org/chromedriver/logging

Also, make sure to upgrade Chromedriver version to 2.31. It can be downloaded from https://sites.google.com/a/chromium.org/chromedriver/downloads

Hello,

I have upgraded my selenium-standalone-server to 3.5.0 from 2.53.1 and it started working.

As i said earlier i am already using Chromedriver version to 2.31.

Is there any selenium-standalone-server version recommendation for 61.0.3163.31+ ?

Thanks,
Karishma

Outputs:
# ls /usr/local/
bin  etc  games  include  lib  man  sbin  share  src

# /opt/google/chrome-beta/google-chrome-beta
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
Trace/breakpoint trap

# /selenium/chromedriver --verbose --log-path=chromedriver.log
Starting ChromeDriver 2.31.488763 (092de99f48a300323ecf8c2a4e2e7cab51de5ba8) on port 9515
Only local connections are allowed.

^C

# ls -ltr
total 0
-rw-r--r-- 1 root root 0 Aug 15 02:10 chromedriver.log

Hmm, strange. Selenium webdriver version shouldn't affect Chromedriver testing. Having said that, it is always recommended to use the latest versions of webdriver as well as Chromedriver. There is active development going on with new features being added to both Selenium webdriver & Chromedriver and bugs will not be fixed in previous versions.

However, good to know that your issue is resolved. Closing this issue.