Upgrade to v93 Chrome and chromedriver - Tests failing

1104 views
Skip to first unread message

pgcl...@gmail.com

unread,
Sep 9, 2021, 4:53:19 AMSep 9
to ChromeDriver Users
Hi,

I have tests running in Robot and WebDriverIO.  

Our test agents recently auto updated to chrome 93 and we have a script to install the corresponding chromedriver to match so in this case - ChromeDriver 93.0.4577.15

Since this all of our tests are failing in Robot with the following error:

SessionNotCreatedException: Message: session not created
from timeout: Timed out receiving message from renderer: 600.000

WebriverIO tests hang on launching the browser and eventually time out.

The tests are running under a service account on the test agents.

Thanks,
Paddy


Philippe Hainaut

unread,
Sep 9, 2021, 6:14:16 AMSep 9
to ChromeDriver Users
Hello i have the same problems since update chrome and chrome driver.(timeout)
We use robot in jenkins jobs and the appears in this context.
Using robot command directly in terminal pycharm for example no problems

Justin Lloyd

unread,
Sep 9, 2021, 12:31:22 PMSep 9
to ChromeDriver Users
I believe we are seeing the same issue caused by an update to Chrome 93. We have a service account running a ServiceNow agent which launches ChromeDriver. When the agent is being run as a Windows service we see a timeout trying to communicate with Chrome. When we run the agent with an interactive session everything works as it had been.

Our automations were running on a schedule every few hours without issue until Chrome 93 installed. Like the parent poster, we tried upgrading our ChromeDriver. Tried a couple versions, including 93.0.4577.63, which matches our Chrome version. Since 93 we have not been able to communicate with Chrome without an interactive logon. Windows Server 2019.

John Daly

unread,
Sep 9, 2021, 12:47:32 PMSep 9
to ChromeDriver Users
I believe I am seeing the same issue since Chrome Browser was updated to version 93. I also updated Chromedriver and tried both of the following versions:
    chromedriver_93.0.4577.15
    chromedriver_93.0.4577.63
As Justin Lloyd reported, my process is run as a windows service. When I run it from a login session, it works as expected. 

Does anyone know if this has been reported as  bug?

Philippe Hainaut

unread,
Sep 10, 2021, 4:09:04 AMSep 10
to ChromeDriver Users

hello --disable gpu option starting chrome driver doesn't work in terminal or junkins jobs with robot.

I used it by
Call Method ${options} add_argument --disable gpu

Create WebDriver Chrome chrome_options=${options}
in comon.robot
Le jeudi 9 septembre 2021 à 10:53:19 UTC+2, pgcl...@gmail.com a écrit :

pgcl...@gmail.com

unread,
Sep 10, 2021, 4:26:09 AMSep 10
to ChromeDriver Users
Check this conversation for potential solution.  Worked for me - https://groups.google.com/g/chromedriver-users/c/F6QoJkegYNc

pgcl...@gmail.com

unread,
Sep 10, 2021, 6:42:26 AMSep 10
to ChromeDriver Users

Thanks will try that.
On Friday, 10 September 2021 at 09:09:04 UTC+1 Philippe Hainaut wrote:

suchi vashi

unread,
Sep 10, 2021, 6:55:48 AMSep 10
to ChromeDriver Users
Hi,

For robot , the render message issue is not resolved after adding --disable gpu for terminal execution through Jenkins.
could some one please help ?

will there be any official fix for this issue in chrome driver next update?

Thanks,
Suchi D.

Maksim Sadym

unread,
Sep 10, 2021, 7:15:25 AMSep 10
to ChromeDriver Users
Please report an issue (ideally with a minimal repro example) in the bug tracker: https://bugs.chromium.org/p/chromedriver

Alfonso Alarcón

unread,
Sep 10, 2021, 7:48:14 AMSep 10
to ChromeDriver Users
Hi, 
I have the same issue with Chrome Version 93.0.4577.63 and chromedriver_93.0.4577.63.
In my case the issue is reproduced launching a Jenkins job with Python:

Traceback (most recent call last): File "C:\Windows\TEMP\shiningpanda8019221436339212183.py", line 11, in <module> driver = webdriver.Chrome(executable_path="C:/chromedriver_win32/chromedriver.exe") File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37-32\lib\site-packages\selenium\webdriver\chrome\webdriver.py", line 81, in __init__ desired_capabilities=desired_capabilities) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 157, in __init__ self.start_session(capabilities, browser_profile) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 252, in start_session response = self.execute(Command.NEW_SESSION, parameters) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37-32\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute self.error_handler.check_response(response) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37-32\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.SessionNotCreatedException: Message: session not created from timeout: Timed out receiving message from renderer: 600.000 (Session info: chrome=93.0.4577.63)

 My Jenkins agent is in mode service.

Before the Chrome Version 93.0.4577.63 the job was working correctly.

Best regards,

Alfonso

vinay kumar

unread,
Sep 10, 2021, 1:40:03 PMSep 10
to ChromeDriver Users
Hi ,
I am also facing same above issue on Jenkins -- chromedriver 93 with java. Please help , for now resolved with --no-sandbox attribute which is not recommended. 
ChromeDriver was started successfully. [1631255910.627][SEVERE]: Timed out receiving message from renderer: 600.000
org.openqa.selenium.SessionNotCreatedException: session not created from timeout: Timed out receiving message from renderer: 600.000 (Session info: chrome=93.0.4577.63) Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
remote stacktrace: Backtrace: Ordinal0 [0x00C1D403+2479107] Ordinal0 [0x00BB7D51+2063697] Ordinal0 [0x00AC20C8+1056968] Ordinal0 [0x00AB499D+1001885] Ordinal0 [0x00AB39ED+997869] Ordinal0 [0x00AB3CA6+998566] Ordinal0 [0x00AB3595+996757] Ordinal0 [0x00ABE184+1040772] Ordinal0 [0x00AB3551+996689] Ordinal0 [0x00AB4476+1000566] Ordinal0 [0x00AB39ED+997869] Ordinal0 [0x00AB3CA6+998566] Ordinal0 [0x00AB3595+996757] Ordinal0 [0x00ABC16A+1032554] Ordinal0 [0x00AB3551+996689] Ordinal0 [0x00AB4476+1000566] Ordinal0 [0x00AB39ED+997869] Ordinal0 [0x00AB3CA6+998566] Ordinal0 [0x00AB3595+996757] Ordinal0 [0x00AB9FF9+1023993] Ordinal0 [0x00AB3551+996689] Ordinal0 [0x00AB4476+1000566]

Alfonso Alarcón

unread,
Sep 13, 2021, 2:33:55 AMSep 13
to ChromeDriver Users
I have open the issue: https://bugs.chromium.org/p/chromedriver/issues/detail?id=3910

Best Regards,

Alfonso

Charvi Gaur

unread,
Sep 14, 2021, 9:11:02 AMSep 14
to ChromeDriver Users
While running windows service that scraps data using selenium chromedriver is required and the latest update of chromedriver 93 is not letting the windows service to run.
Getting session timeout exceeded error. When is this error expected to be resolved?

Charvi Gaur

unread,
Sep 14, 2021, 9:11:08 AMSep 14
to ChromeDriver Users
While running windows service that scraps data using selenium chromedriver is required and the latest update of chromedriver 93 is not letting the windows service to run.
Getting session timeout exceeded error. When is this error expected to be resolved?
On Monday, September 13, 2021 at 12:03:55 PM UTC+5:30 Alfonso Alarcón wrote:

Ruben

unread,
Sep 15, 2021, 12:25:44 PMSep 15
to ChromeDriver Users
i have chrome options this way and works fine. 
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless", "--disable-gpu", "--window-size=1920,1200",
"--ignore-certificate-errors", "--disable-extensions", "--no-sandbox", "--disable-dev-shm-usage");
options.setCapability(CapabilityType.UNEXPECTED_ALERT_BEHAVIOUR, UnexpectedAlertBehaviour.IGNORE);
driver = new ChromeDriver(options);

Tze An Chua

unread,
Sep 19, 2021, 11:53:22 PMSep 19
to ChromeDriver Users
I'm experiencing this issue as well, currently changing browser from 'chrome' to 'headlesschrome' in robot to workaround it.

sach 323

unread,
Sep 21, 2021, 6:49:18 PMSep 21
to ChromeDriver Users
We are also started seeing this issue after upgrading to chrome driver 93
OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:57298/session/d9aa5e844fdda398fb15ed51b9842a26/screenshot timed out after 60 seconds. 

Chester Ayala

unread,
Sep 23, 2021, 2:39:12 AMSep 23
to ChromeDriver Users
We also started experiencing this issue as well when we upgraded chrome driver to version 93 on robotframework tests.

The temporary fix for this on robotframewotk is to have --disable-gpu
Open Browser    ${URL}    ${BROWSER}    options=add_argument("--disable-gpu")
Reply all
Reply to author
Forward
0 new messages