search

FuckTheWorld / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

Getting "Timed out receiving message from renderer" on ExecuteScript #848

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
For quite some time already, we have been getting random 
WebDriverTimeoutException - "Timed out receiving message from renderer" 
(See below for the actual exception) exceptions in our tests with 
RemoteWebDriver.

I finally managed to make a test case to reproduce the issue semi-reliably 
against two different systems. Please see the attached test.cs (C# console 
application) as well the selenium and chromedriver logs.
WebDriverTimeoutException is thrown on one of the three ExecuteScript methods 
randomly, roughly 50% of the times we run it.
Don't mind the weird structure as it's the only one that worked to reproduce 
the issue semi-reliably against the following two machines (test.cs itself was 
running on a Windows machine):

Fedora 19:
 Chrome: 36.0.1985.103
 Selenium Server: 2.42.2
 Chromedriver: 2.10.267518
 C# bindings: 2.42.0

Ubuntu 14.04 LTS:
 Chrome: 37.0.2062.3 (I am aware that 37 is not officially supported by 2.10.  but that's what we had...)
 Selenium Server: 2.42.2
 Chromedriver: 2.10.267518
 C# bindings: 2.42.0

Strangely enough the attached test seem to work flawlessly against a Windows 
Server running Chrome 34.0.1847.137. The issue still happens there occasionally 
I just wasn't able to reproduce it with the attached test.

The exception:
OpenQA.Selenium.WebDriverTimeoutException: timeout: Timed out receiving message 
from renderer: 0.000
  (Session info: chrome=36.0.1985.103)
  (Driver info: chromedriver=2.10.267518,platform=Linux 3.14.4-100.fc19.x86_64 x86_64) (WARNING: The server did not provide any stacktrace i
nformation)
Command duration or timeout: 74 milliseconds
Build info: version: '2.42.2', revision: '6a6995d', time: '2014-06-03 17:42:03'
System info: host: 'N/A', ip: 'N/A', os.name: 'Linux', os.arch: 'amd64', 
os.version: '3.14.4-100.fc19.x86_64', java.version: '1.8.0_05'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, 
chrome={userDataDir=/tmp/.com.google.Chrome.sMxOLG}, takesHeapSnapshot=true,
databaseEnabled=false, handlesAlerts=true, version=36.0.1985.103, 
platform=LINUX, browserConnectionEnabled=false, nativeEvents=true, acceptSsl
Certs=true, locationContextEnabled=true, webStorageEnabled=true, 
browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelect
orsEnabled=true}]
Session ID: f833bf59daf736eb2fc223af11dc4c29
   at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWebDriver.ExecuteScriptCommand(String script, String commandName, Object[] args)
   at OpenQA.Selenium.Remote.RemoteWebDriver.ExecuteScript(String script, Object[] args)

Original issue reported on code.google.com by rom...@gmail.com on 12 Jul 2014 at 10:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Issue 846 has been merged into this issue.

Original comment by pshe...@chromium.org on 16 Jul 2014 at 10:27

GoogleCodeExporter commented 9 years ago 
I'm able to reproduce the following 100% of the times.
The test case just loads the webpage and does nothing more. The page has plenty 
of wrong URLs to assets therefore many stylesheets/scripts/images don't load. 
When the test is run again the 'working' version of the website, everything 
works fine.

{ [ScriptTimeoutError: timeout: Timed out receiving message from renderer: 
10.000
  (Session info: chrome=37.0.2062.120)
  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 40.28 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:33'
System info: host: 'win7', ip: '192.168.222.101', os.name: 'Windows 7', 
os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_20'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, 
chrome={userDataDir=C:\Users\ADMINI~1\AppData\Local\Temp\scoped_dir4024_14204}, 
takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, 
version=37.0.2062.120, platform=XP, browserConnectionEnabled=false, 
nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, 
webStorageEnabled=true, browserName=chrome, takesScreenshot=true, 
javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: abc4b498b2f6a4790ccf69e69fe2fc31]
  code: 28,
  state: 'script timeout',
  message: 'timeout: Timed out receiving message from renderer: 10.000\n  (Session info: chrome=37.0.2062.120)\n  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86) (WARNING: The server did not provide any stacktrace information)\nCommand duration or timeout: 40.28 seconds\nBuild info: version: \'2.43.1\', revision: \'5163bce\', time: \'2014-09-10 16:27:33\'\nSystem info: host: \'win7\', ip: \'192.168.222.101\', os.name: \'Windows 7\', os.arch: \'x86\', os.version: \'6.1\', java.version: \'1.8.0_20\'\nDriver info: org.openqa.selenium.chrome.ChromeDriver\nCapabilities [{applicationCacheEnabled=false, rotatable=false, chrome={userDataDir=C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\scoped_dir4024_14204}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, version=37.0.2062.120, platform=XP, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]\nSession ID: abc4b498b2f6a4790ccf69e69fe2fc31',
  name: 'ScriptTimeoutError',
  stack: 'ScriptTimeoutError: timeout: Timed out receiving message from renderer: 10.000\n  (Session info: chrome=37.0.2062.120)\n  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86) (WARNING: The server did not provide any stacktrace information)\nCommand duration or timeout: 40.28 seconds\nBuild info: version: \'2.43.1\', revision: \'5163bce\', time: \'2014-09-10 16:27:33\'\nSystem info: host: \'win7\', ip: \'192.168.222.101\', os.name: \'Windows 7\', os.arch: \'x86\', os.version: \'6.1\', java.version: \'1.8.0_20\'\nDriver info: org.openqa.selenium.chrome.ChromeDriver\nCapabilities [{applicationCacheEnabled=false, rotatable=false, chrome={userDataDir=C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\scoped_dir4024_14204}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, version=37.0.2062.120, platform=XP, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]\nSession ID: abc4b498b2f6a4790ccf69e69fe2fc31\n    at new bot.Error (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/atoms/error.js:113:18)\n    at Object.bot.response.checkResponse (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/atoms/response.js:106:9)\n    at webdriver.WebDriver.schedule (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:319:20)\n    at goog.partial (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/goog/base.js:1582:15)\n    at webdriver.promise.ControlFlow.runInNewFrame_ (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/promise.js:1640:20)\n    at notify (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/promise.js:444:12)\n    at notifyAll (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/promise.js:422:7)\n    at resolve (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/promise.js:400:7)\n    at fulfill (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/promise.js:512:5)\n    at /Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/promise.js:1507:10\n==== async task ====\nWebDriver.navigate().to(http://phishbuster.dev:9000)\n    at webdriver.WebDriver.schedule (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:302:15)\n    at webdriver.WebDriver.Navigation.to (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:969:23)\n    at webdriver.WebDriver.get (/Users/ettore/Workspace/phishbuster/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:661:26)\n    at loadTest [as run] (/Users/ettore/Workspace/phishbuster/fisherman.js:44:16)\n    at Test.execute (/Users/ettore/Workspace/phishbuster/fisherman.js:358:32)\n    at doResolve (/Users/ettore/Workspace/phishbuster/node_modules/promise/core.js:91:5)\n    at new Promise (/Users/ettore/Workspace/phishbuster/node_modules/promise/core.js:71:3)\n    at Test.execute (/Users/ettore/Workspace/phishbuster/fisherman.js:353:12)\n    at processTestRequests [as _onTimeout] (/Users/ettore/Workspace/phishbuster/fisherman.js:1020:18)',
  webdriver_promise_error_: true }

Original comment by ete....@gmail.com on 1 Oct 2014 at 2:12

GoogleCodeExporter commented 9 years ago 
I have the same issue
os.name: 'Windows 7'

[379.701][SEVERE]: Timed out receiving message from renderer: 137.675
[389.703][SEVERE]: Timed out receiving message from renderer: 10.000
[689.721][SEVERE]: Timed out receiving message from renderer: 300.000
[699.724][SEVERE]: Timed out receiving message from renderer: 10.000
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from 
renderer: 10.000
  (Session info: chrome=37.0.2062.124)
  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 310.14 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58'
System info: host: 'TESTING215', ip: '192.168.101.000', os.name: 'Windows 7', 
os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_45'
Session ID: d2620fdbc7ba916d34cbfe8b09709e10
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, 
browserName=chrome, 
chrome={userDataDir=C:\Users\HARIPR~1\AppData\Local\Temp\scoped_dir5392_9182}, 
rotatable=false, locationContextEnabled=true, version=37.0.2062.124, 
takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, 
handlesAlerts=true, browserConnectionEnabled=false, nativeEvents=true, 
webStorageEnabled=true, applicationCacheEnabled=false, takesScreenshot=true}]
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from 
renderer: 10.000
  (Session info: chrome=37.0.2062.124)
  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 310.14 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58'
System info: host: 'TESTING215', ip: '192.168.101.000', os.name: 'Windows 7', 
os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_45'
Session ID: d2620fdbc7ba916d34cbfe8b09709e10
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, 
browserName=chrome, 
chrome={userDataDir=C:\Users\HARIPR~1\AppData\Local\Temp\scoped_dir5392_9182}, 
rotatable=false, locationContextEnabled=true, version=37.0.2062.124, 
takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, 
handlesAlerts=true, browserConnectionEnabled=false, nativeEvents=true, 
webStorageEnabled=true, applicationCacheEnabled=false, takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:614)
    at org.openqa.selenium.remote.RemoteWebDriver.getScreenshotAs(RemoteWebDriver.java:324)
    at ECV6_Excelicare.ECV6_SmokeTest.CaptureScreenshot(ECV6_SmokeTest.java:4689)
    at ECV6_Excelicare.ECV6_SmokeTest.Patient_Registration(ECV6_SmokeTest.java:92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
    at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
    at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
    at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
    at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
    at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
    at org.testng.TestRunner.privateRun(TestRunner.java:767)
    at org.testng.TestRunner.run(TestRunner.java:617)
    at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
    at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
    at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
    at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
[1004.301][SEVERE]: Timed out receiving message from renderer: 230.172
[1014.304][SEVERE]: Timed out receiving message from renderer: 10.000

This is the first time I've faced this issue.

Note : I have blocked third party ads.Updated the chrome and standalone.

Steps:
1) Loaded the page.
2) Waited for the page load to complete .
3) Tried to click the element on the page
4) Now, Got the above error message.

Original comment by haripras...@gmail.com on 13 Oct 2014 at 1:33

GoogleCodeExporter commented 9 years ago 
it happens on chrome version 37,
selenium version 2.43.0

Original comment by haripras...@gmail.com on 13 Oct 2014 at 1:37

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago 
Issue is with executeAsyncScript. If we call executeScript, running 
sucessfully, verfied in Ubuntu

please find below code:
ChromeOptions options = new ChromeOptions();
WebDriver driver=null;
try {
driver= new RemoteWebDriver(new URL("http://0.0.0.0:4444/wd/hub"), 
DesiredCapabilities.chrome());
} catch (MalformedURLException e) {
e.printStackTrace();
}
driver.manage().timeouts().pageLoadTimeout(60000, TimeUnit.MILLISECONDS);
driver.navigate().to("http://albar.co.il");
driver.manage().timeouts().pageLoadTimeout(0, TimeUnit.MILLISECONDS);
System.out.println("Timings:"+((JavascriptExecutor)driver).executeScript("return
 {navigationStart: window.performance.timing.navigationStart};"));

driver.manage().timeouts().pageLoadTimeout(60000, TimeUnit.MILLISECONDS);
driver.findElement(By.id("BoxesPanel5_boxes_ctl00_0_submit_0")).click();
driver.manage().timeouts().pageLoadTimeout(0, TimeUnit.MILLISECONDS);

System.out.println("Timings:"+((JavascriptExecutor)driver).executeScript("return
 {navigationStart: window.performance.timing.navigationStart}"));

driver.manage().timeouts().pageLoadTimeout(60000, TimeUnit.MILLISECONDS);
driver.findElement(By.linkText("סניפים")).click();
driver.manage().timeouts().pageLoadTimeout(0, TimeUnit.MILLISECONDS);

System.out.println("Timings:"+((JavascriptExecutor)driver).executeScript("return
 {navigationStart: window.performance.timing.navigationStart}"));

Original comment by ssudunag...@chromium.org on 12 Mar 2015 at 12:24