--
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.
You received this message because you are subscribed to a topic in the Google Groups "ChromeDriver Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedriver-users/Y90geNHYj6c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedriver-us...@googlegroups.com.
Any update on this?
I've recreated a similar problem to that reported by Sowjanya and Ravi. It isn't crashing, but chromedriver seems to be hanging while navigating.
Here is the chromedriver log with --verbose: https://www.dropbox.com/s/3klz52rtijzcezz/chromedriver.log?dl=0. Please let me know how to send it to you if you can't access dropbox.
The last entry in the log seems to be sending a Runtime.enable message with no sessionId. And never getting a response:
[1541626970.742][DEBUG]: DevTools WebSocket Command: Runtime.enable (id=7) 1E94D396D69AEEC4A102311001D4D64C {
}
[1541626970.742][DEBUG]: DevTools WebSocket Command: Target.sendMessageToTarget (id=133) 0186C658E94D49107B6C16670FE71A31 {
"message": "{\"id\":7,\"method\":\"Runtime.enable\",\"params\":{}}",
"sessionId": "1E94D396D69AEEC4A102311001D4D64C"
}
[1541626970.743][DEBUG]: DevTools WebSocket Command: Runtime.enable (id=7) {
}
[1541626970.743][DEBUG]: DevTools WebSocket Command: Target.sendMessageToTarget (id=134) 0186C658E94D49107B6C16670FE71A31 {
"message": "{\"id\":7,\"method\":\"Runtime.enable\",\"params\":{}}",
"sessionId": ""
}
Don't know if this helps.
Regards
Paul
I have been expereincing this same issue of chromedriver gets hang on chrome version 70.0.3538.77
chromedriver version used is : 2.37.544315 (not the latest)
For me , it was also due to some kind behaviour happening at the web application end (because I manually verified it )
I observed that when there is an action happens, like 'click on a buttton', the page navigation in the browser is not really a smooth one. The page navigation happens just fine, but the browser is not really giving a hint to the user that it is loading the page, like showing a loading spinning gear in the browser tab which used to appear earlier.
so when the same action is automated with chromedriver and chrome, some where chromedriver also is not getting clue/hint that the page navigation has started or dome. and it just waits and looks as hang for us, finally giving all ConnectException: Connection refused errors.
and same thing is what shown in the chromedriver logs as well,it just stays there
[1541407139.835][INFO]: Waiting for pending navigations...
[1541407139.835][INFO]: Done waiting for pending navigations. Status: ok
[1541407139.917][INFO]: Waiting for pending navigations...
So you may also check this, if this is the case in your end or not ?
Hi John Chen,
Also I would like to ask, how does the chromedriver determines that page navigation has happened and it is done waiting for page navigation , can you please share the logic, so i can also try the same manully at my application end and try to gather some more info for debugging this issue
Thanks & Warm Regards
Musaffir
chromeOptions.setExperimentalOption("useAutomationExtension", false);
Initial indications look promising, so giving it a soak test. Do you have this option set, Musaffir?
Regards
Paul
Hi Paul,
I dont have this set
I can set it and run tests
will come back here with the result
Please let us know how your testing going with this as well
Warm Regards
Musaffir
Failed doing the Navigate as before:
[1541778388.205][INFO]: [e4f3f4ad201ebdfe14cfcbcc97455959] COMMAND Navigate {
"url": "https://eu7.salesforce.com/0030J00002D8ovjQAB"
}
[1541778388.205][INFO]: Waiting for pending navigations...
[1541778388.205][INFO]: Done waiting for pending navigations. Status: ok
[1541778388.802][INFO]: Waiting for pending navigations...
John, please take a look at the verbose log I posted when you have a chance (https://www.dropbox.com/s/3klz52rtijzcezz/chromedriver.log?dl=0) and let me know if you have any suggestions.
Regards
Paul
It looks same at my end too
Setting "useAutomationExtension=false" option removed, did not help
Thanks
We have worked out what's causing the crash ... chromedriver is trying to use a DevToolsClient that has been disposed.
I suspect it is because a "Target.detachedFromTarget" message is received (causing the DevToolsClient to be closed) while a "DOM.getDocument" request is still in-flight. It is crashing while waiting to the "DOM.getDocument" response.
I've worked around this by setting the DevToolsClient to "detached" state rather than disposing. But this isn't a long-term solution. The patched driver is here: https://www.dropbox.com/s/diudrx540dvqvyh/chromedriver.exe?dl=0.
John, let's discuss the proper solution for this when you have some time.
Regards
Paul
[Chromedriver] Error: No Chromedriver found that can automate Chrome '70.0.3538'. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details.
[Chromedriver] at Object.wrappedLogger.errorAndThrow (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[Chromedriver] at Chromedriver.errorAndThrow [as getCompatibleChromedriver] (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:289:11)
[Chromedriver] at process._tickCallback (internal/process/next_tick.js:68:7)
[Chromedriver] Error: No Chromedriver found that can automate Chrome '70.0.3538'. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details.
[Chromedriver] at Object.wrappedLogger.errorAndThrow (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[Chromedriver] at Chromedriver.errorAndThrow [as start] (/Applications/Appium.app/Contents/Resources/app/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:441:11)
[Chromedriver] at process._tickCallback (internal/process/next_tick.js:68:7)