Issue metadata
Sign in to add a comment
|
Chrome UI automation: "disconnected: unable to connect to renderer" error message on browser start
Reported by
stryh.pa...@gmail.com,
Sep 19 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.91 Safari/537.36 Steps to reproduce the problem: 1. Update chrome version to chrome=62.0.3202.18 2. Run any UI test (headless or non-headless) What is the expected behavior? Test is being executed What went wrong? Chrome browser is open, but there is an error in logs and browser is hanged: Caused by: 'disconnected: unable to connect to renderer (Session info: chrome=62.0.3202.18) (Driver info: chromedriver=2.32.498550 Did this work before? Yes It works ok for Chrome 61 Chrome version: 62.0.3202.18 64-bit Channel: stable OS Version: 6.3 Flash Version:
,
Sep 19 2017
,
Sep 20 2017
Since it is related to browser automation(Selenium) , hence adding TE-NeedsTriageHelp for further triage.
,
Sep 20 2017
I got the same running on Ubuntu trying out the beta channel.
,
Sep 20 2017
,
Sep 20 2017
stryh.pavel@, Do you see the issue right while launching Chrome through Chromedriver or it appears during a particular command? Could you please provide reproducible test and chromedriver verbose log?
,
Sep 21 2017
@gmanikpure@chromium.org , It happens on chromeDriver creation - Browser start. 1) Test: I initialize a chromeDriver var driver = new ChromeDriver(dllPath, options, TimeSpan.FromMilliseconds(180)) 2) Run it 3) Browser is open and at the same time I get the error. So, it happens on an initialization step Logs cannot be attached, as I downgraded to v.61. Sorry.
,
Sep 21 2017
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
,
Sep 21 2017
Appreciate your response! Unfortunately, I am not able to reproduce the issue on Chrome beta v62.0.3202.29 with Chromedriver v2.32. We also run continuous tests on all the current channels Chrome builds including the nightly build against Chromedriver v2.32+ and so far we haven't encountered this issue. Are you passing any flags using ChromeOptions?
,
Sep 21 2017
I can reproduce with: (Session info: chrome=63.0.3221.0) (Driver info: chromedriver=2.32.498537 (cb2f855cbc7b82e20387eaf9a43f6b99b6105061),platform=Mac OS X 10.12.6 x86_64) Attached the Chromedriver log.
,
Sep 21 2017
phedenskog@, Thanks for providing the log. Your issue is related to https://bugs.chromium.org/p/chromedriver/issues/detail?id=1918. And the fix will be available as a part of Chromedriver v2.33 release.
,
Oct 5 2017
regarding comment#11, Chromedriver v2.33 has been released. You can download it from https://sites.google.com/a/chromium.org/chromedriver/downloads Closing this issue. However, please feel free to reopen if you see the issue with the latest chromedriver version. Make sure to provide reproducible test. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by stryh.pa...@gmail.com
, Sep 19 2017