Timed out receiving message from renderer error

[GoogleCodeExporter]

I am running some jobs in Jenkins and I notice that I keep getting "Timed out 
receiving message from renderer" and is causing many failures.

I noticed that the Chrome browser is starting up with data:, in the URL and I 
understand this is normal, however I notice that this is taking a long time to 
finish loading as I see the spinner in its tab.

Has anyone ever seen this, or know what could be causing this problem?

Original issue reported on code.google.com by miahj13 on 7 Jun 2014 at 9:46

Attachments:

• Capture.PNG

[GoogleCodeExporter]

I've also started running into this issue. In our case, the tests fail on 
random pages.  One of the latest case was when calling webDriver.Url = "<page 
URL>"; to navigate to a page.

Specs:
Windows7 SP1, WebDriver v2.41, C#, ChromeDriver v2.10, Chrome v35.0.1916.114  

Original comment by radek.bo...@gmail.com on 9 Jun 2014 at 5:51

[GoogleCodeExporter]

I am am also seeing this issue frequently have been noticing it from chrome 33 
version.Mostly i see it on page load. 

This is occurs while i manually kick off scripts while watching the browser and 
also during headless executions.

I am on webdriver 2.39 , chrome 35.0.1916.114 windows 7

Original comment by jselen...@gmail.com on 13 Jun 2014 at 6:43

[GoogleCodeExporter]

I am seeing the same thing:

Caused by: org.openqa.selenium.TimeoutException: timeout: Timed out receiving 
message from renderer: 300.000
  (Session info: chrome=36.0.1985.125)
  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)

Selenium is starting up with Spring which runs with our junit tests as part of 
a maven build. The maven build is being run by jenkins which is running as 
windows service.

This seems to be happening when calling open on a WebDriverBackedSelenium 
instance. And is pretty much at the start of the test. We don't use a new 
chrome window for each test though (to save closing and reopening each time). 
So could be caused by something hanging from a previous test in some way?

Original comment by martin.c...@gamma.co.uk on 12 Aug 2014 at 4:00

[GoogleCodeExporter]

I see this with 100% consistent repro on my development machine at work along 
with a few other test and coworker machines. I tried rebuilding some new VMs 
with near identical configurations but they don't repro, ChromeDriver works 
fine on those, so I couldn't pin it down to any piece of software or system 
setting. But it does seem machine specific somehow.

Happens just after calling 'RemoteWebDriver driver = new ChromeDriver()'. The 
call returns successfully and Chrome launches but it just sits there spinning 
with 'Loading...' title and 'data:,' in the address bar. Manual navigation in 
this instance of Chrome by typing in new addresses, opening new tabs and 
windows and attempting to navigate to different URLs doesn't navigate or open 
any pages. All activity just appears hung until this browser instance is closed.

If I do try to navigate using the driver, e.g. 
'remoteWebDriver.Navigate().GoToUrl(url)' then I eventually get the 'Timed out 
receiving message from renderer: 600.000' message repeatedly until the browser 
instance is closed.



Selenium version 2.43 (C#)
ChromeDriver version 2.10.267521
Chrome version 37.0.2062.124 m
Windows 8.1 x64


Please let me know how I can help you debug this further, by grabbing stack 
traces, installing private builds, collecting logs, etc.

Original comment by rykno...@gmail.com on 29 Sep 2014 at 8:49

[GoogleCodeExporter]

Hi,

I am also getting this for all my tests which involve the ChromeDriver.  It 
appeared to start suddenly a couple of weeks ago with no changes to the java 
project in git. One other person has access to the build server (Jenbkins) 
although he says there have been no changes and I can't see anything obvious.  
The tests were working for a couple of months without issue and now every one 
fails along the lines of 

org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from 
renderer: 600.000
  (Session info: chrome=38.0.2125.104)
  (Driver info: chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 599.99 seconds

os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1', 
java.version: '1.7.0_45'
selenium version 2.37.1

Selenium is starting up with Spring which runs with our junit tests as part of 
a maven build. The maven build is being run by jenkins which is running as 
windows service under the Local system account.

Any ideas !?

Original comment by BenKDish...@gmail.com on 3 Nov 2014 at 10:50

[GoogleCodeExporter]

Hi,

I am also getting this issue while starting the test. 

timeout: Timed out receiving message from renderer: 291.157
(Session info: chrome=39.0.2171.95)
(Driver info: chromedriver=2.12.301325 ,platform=Windows NT 6.1 SP1 x86_64) 
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 300.28 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:33'
os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: 
'1.7.0_51' .


This issue may be because of 32 bit chromedriver running in 64 bit windows 
machine ?

Original comment by kkselv...@gmail.com on 2 Jan 2015 at 9:14

[GoogleCodeExporter]

I observe similar behavior with chromedriver versions 2.13 and 2.14.

Everything freezes right after driver initialization and never recovers. Chrome 
is started and I see 'data:,' in URL bar, but the whole browser window is 
grayed out and marked as Not Responding. The following error is reported in the 
console:
Starting ChromeDriver 2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf) on 
port 11355
Only local connections are allowed.
[603.306][SEVERE]: Timed out receiving message from renderer: 600.000
[1203.306][SEVERE]: Timed out receiving message from renderer: 600.000

Running a 64bit Windows 7, Chrome 40, selenium 2.44.0 

I'm reverting back to 2.12 which is the last working version for me.

Original comment by aa.iva...@gmail.com on 4 Feb 2015 at 12:06

[GoogleCodeExporter]

Upgraded to 2.14, and the same Selenium test which used to work fine for me now 
hangs in Chrome.  I only see the word "data;" in the Chrome browser.  I see a 
similar Chrome hang when I run the sample "Web-Component-Test" (WCT) test 
described in 
https://www.polymer-project.org/articles/unit-testing-elements.html#tutorial.

Original comment by billk2ch...@gmail.com on 16 Feb 2015 at 3:39

[GoogleCodeExporter]

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:18

• Changed state: Unconfirmed

[GoogleCodeExporter]

Even we are facing the same issue repeatedly in our application when we use 
selenium. I am using chrome driver 2.14 and selenium 2.45.0. Can you please 
look into this.

Original comment by ravikant...@gmail.com on 23 Feb 2015 at 1:30

[GoogleCodeExporter]

This was happening to me.  I finally figured out where my problem was but it 
appears that webdriver on chrome does not recover or even respect the timeout 
values set when trying to do a call on a driver object that does not exist.  
Meaning lets suppose you have a web app that spawns multiple windows, and one 
of the windows auto closes, if you are still on that window handle and try to 
call getTitle() for instance on that window this problem will occur.  

org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from 
renderer: 600.000
  (Session info: chrome=40.0.2214.115)
  (Driver info: chromedriver=2.9.248315,platform=Windows NT 6.2 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 600.02 seconds
Build info: version: '2.44.0', revision: 
'76d78cf323ce037c5f92db6c1bba601c2ac43ad8', time: '2014-10-23 13:11:40'
System info: host: 'VC2CRTPA021503', ip: '10.96.55.25', os.name: 'Windows 
Server 2012', os.arch: 'amd64', os.version: '6.2', java.version: '1.7.0_55'
Session ID: 46e6ab11cbcb48baca9765f8d9fd7624
Driver info: org.openqa.selenium.chrome.ChromeDriver

Original comment by jtorres...@gmail.com on 4 Mar 2015 at 7:08

[GoogleCodeExporter]

Unable to reproduce the issue with with chrome:41.0.2272.89 and 
chromedriver:2.14, selenium version-2.45 on Windows 7 and Ubuntu 14
Please try again and let us know if we differ from what you are doing

Original comment by ssudunag...@chromium.org on 18 Mar 2015 at 4:48

[GoogleCodeExporter]

After completing the upgrades of all bits in the toolchain, I gave it another 
try with my setup:
Win 7 64bit, Chrome 41.0.2272.101, chromedriver 2.14, selenium-java 2.45.0

So far I've been unable reproduce the the issue anymore. Browser starts, driver 
initializes and tests are running.

Original comment by aa.iva...@gmail.com on 21 Mar 2015 at 1:33

[GoogleCodeExporter]

Getting reproducible inconsistently, and when the chrome driver hangs, all 
other test cases are getting skipped. 

org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from 
renderer: 600.000
  (Session info: chrome=41.0.2272.101)
  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 600.02 seconds
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:03:00'
System info: host: 'xxxx-automation', ip: 'xx.xxx.xx.xxx', os.name: 'Windows 
7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_40'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, 
mobileEmulationEnabled=false, 
chrome={userDataDir=C:\Users\ADMINI~1\AppData\Local\Temp\scoped_dir4624_16646}, 
takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, 
version=41.0.2272.101, platform=XP, browserConnectionEnabled=false, 
nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, 
webStorageEnabled=true, browserName=chrome, takesScreenshot=true, 
javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: d83711ea15151a3c10b60667a1ed9833

When can I expect next ChromeDriver release!!

Original comment by satya.au...@gmail.com on 25 Mar 2015 at 11:55

[AtulUjjwal]

Hi, I am also getting the same error inconsistently. Is there any solution for this ?

TimeoutException: Message: timeout: Timed out receiving message from renderer: 15.000
(Session info: chrome=45.0.2454.101)
(Driver info: chromedriver=2.19.346078 (6f1f0cde889532d48ce8242342d0b84f94b114a1),platform=Windows NT 6.1 SP1 x86_64)

[Jiwari]

@AtulUjjwal
I tried the solution proposed by "jamesonl...@smarttech.com" (discussion link) and it worked.

Downgrading from chromedriver 2.14.313457 to 2.12.301325 (win32) fixed both test agents.

[karlwnw]

I'll share my case:

I had this issue with my Django selenium tests (django==1.7.12 and selenium==2.53.1) with ChromeDriver 2.21.371459 and Google Chrome 48.0.2564.116.

I was able to isolate the issue. In my case it was happening only for pages referencing a static file (an image in a HTML tag for instance http://cdn.local.myproject.net/static/myimage.png) on my custom local cdn domain. The issue was not present if I used a relative path "/static/myimage.png" or localhost "http://127.0.0.1/static/myimage.png so I figured it was a DNS problem.

I was able to bypass the problem by using the --dns-prefetch-disable option of chrome.

Example in Python:

from selenium.webdriver import Chrome
from selenium.webdriver.chrome.options import Options

chrome_options = Options()
chrome_options.add_argument('--dns-prefetch-disable')
driver = Chrome(chrome_options=options)

I don't know if this is the general case but hopefully it can help some of you.

[skptricks]

It causes because page took long time to load , you need add additional line to your chromedriver option. Please refer the below link for more information :
Timed out receiving message from renderer in selenium