New issue
Advanced search Search tips

Issue 764329 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

ChromeDriver non responsive with latest version

Reported by danacohe...@gmail.com, Sep 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
1. use latest chromeDrvier
2. driver.get wil work ok but quickly becomes non responsive

What is the expected behavior?

What went wrong?
it gets stuck and web elements can't be found.

Did this work before? Yes Not sure. worked for me a few days ago

Chrome version: 61.0.3163.79  Channel: stable
OS Version: 6.3
Flash Version:
 
Labels: Needs-Triage-M61
ranjitkan@chromium.org

what do you mean?
Components: Tests>WebDriver
Labels: TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it is related to web driver. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Requesting any dev from Tests>WebDriver team to please have a look into the issue.

Thanks...!!
From researching the issue further on our end, I found out that the real issue is not related to chrome driver.

but is related to Integrated authentication of chrome.
when authenticating with http://user:password@url the login works but then the page becomes non responsive.

I was able to install an older chrome (59.0) and block google update and verified that the integrated authentication does work ok there. so that's the real issue here.

Thanks.
danacohen06@, if you think the issue is not related to Chromedriver, could you please provide manual reproducible test along with the page under testing?

This will help the test team to expedite bug triaging. Thanks!
Labels: Needs-Feedback
Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Since there is no response from the issue reporter for > 2weeks, closing this issue.

Sign in to add a comment