Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago Thanks for the report. Can you summarize the problem and provide a reproducible
test case for us? That will be very helpful.Original comment by kkania@chromium.org on 3 Jul 2013 at 12:10
GoogleCodeExporter
commented
9 years ago I faced the same failure today with the latest chrome driver (v.2.1.2010652) on
Chrome v.28.0.1500.72.
timed out receiving message from renderer
(Session info: chrome=28.0.1500.72)
(Driver info: chromedriver=2.1,platform=Windows NT 5.1 SP3 x86) (WARNING: The
server did not provide any stacktrace information)
Command duration or timeout: 60.02 seconds
Build info: version: '2.32.0', revision: '6c40c18', time: '2013-04-09 17:22:56'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1',
java.version: '1.6.0_31'
Session ID: ed72c4da3717ef31f2eeef9a47923841
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true,
browserName=chrome, chrome={chromedriverVersion=2.1},
rotatable=false, locationContextEnabled=true, version=28.0.1500.72,
cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true,
browserConnectionEnabled=false, nativeEvents=true, webStorageEnabled=true,
applicationCacheEnabled=false, takesScreenshot=true}]
Command duration or timeout: 60.19 seconds
Steps:
1) Loaded the page.
2) Refreshed the page to handle some ad.
3) Waited for the page load to complete (using the custom method which uses
'window.document.readyState')
4) Tried to click the element on the page (once got +ve reply from the wait()
method).
5) Now, Got the above error message.
This is the first time I've faced this issue.
Could anyone brief why it happens.Original comment by davidra...@gmail.com on 29 Jul 2013 at 11:02
GoogleCodeExporter
commented
9 years ago Since chrome 29 I've been forced to use the new chromedriver and now I see this
every once in a while in my tests, chrome used to be our best driver with the
least amount of failures and now this... :(
Usually right after a popup window comes up the test is getting this error when
clicking a link that would close the popup window. I cannot readily duplicate
this but that appears to be the most common case in our environment. I'll be
sure to post a case if I can find an exact case to duplicate it.Original comment by phas...@gmail.com on 26 Aug 2013 at 4:00
GoogleCodeExporter
commented
9 years ago Using
Chrome driver 29
Webdriver 2.35
browser opens and hangs while loading the url, timeout set to 30 secs but didnt
seem to work
during debug, it didnt comeout of Webdriver.Get(url) method.
can you please suggest any solution for thisOriginal comment by vam...@gmail.com on 3 Sep 2013 at 3:53
GoogleCodeExporter
commented
9 years ago [deleted comment][deleted comment][deleted comment]Finally a workaround for me: I had these setting for ChromeDriver for the last
months and they worked. Removing them all now solved the problem:
//driver.manage().timeouts().implicitlyWait(2000, TimeUnit.MILLISECONDS);
//driver.manage().timeouts().pageLoadTimeout(40, TimeUnit.SECONDS);
//driver.manage().timeouts().setScriptTimeout(60, TimeUnit.SECONDS);Original comment by googlewe...@empirica-systeme.de on 10 Sep 2013 at 3:41
GoogleCodeExporter
commented
9 years ago Original comment by st...@chromium.org on 26 Sep 2013 at 10:07
GoogleCodeExporter
commented
9 years ago I have the same issue
timeout: timed out receiving message from renderer
(Session info: chrome=29.0.1547.76)
(Driver info: chromedriver=2.3,platform=Windows NT 5.1 SP3 x86) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 300.62 seconds
Build info: version: '2.35.0', revision: 'c916b9d', time: '2013-08-12 15:42:01'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1',
java.version: '1.7.0_25'
Session ID: 9006ccbd3591f27b9b54589a9a9a6c57
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true,
browserName=chrome, chrome={chromedriverVersion=2.3}, rotatable=false,
locationContextEnabled=true, version=29.0.1547.76, cssSelectorsEnabled=true,
databaseEnabled=true, handlesAlerts=true, browserConnectionEnabled=false,
webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=false,
takesScreenshot=true}]
#0 tests/selenium_tests/php-webdriver/PHPWebDriver/WebDriverBase.php(204):
PHPWebDriver_WebDriverBase::throwException(28, 'timeout: timed ...', Array)
#1 tests/selenium_tests/php-webdriver/PHPWebDriver/WebDriverSession.php(57):
PHPWebDriver_WebDriverBase->curl('POST', '/url', Array, Array)
#2 tests/selenium_tests/TestEngineXcart.php(139):
PHPWebDriver_WebDriverSession->open('http://xcart2-5...')
#3 tests/seltest.so_justonce_condproduct2_same_freeproduct1.bt0115418BJO(117):
TestEngineXcart->openUrl('http://xcart2-5...')
#4 tests/func.selenium.task(126) : eval()'d code(1): bt0115418BJO->test('Add
3_17671.Exp...')
#5 tests/func.selenium.task(126): eval()
#6 tests/gate.code.task(63): require('/u/xcart/eshop_...')
#7 {main}
Original comment by ildar....@gmail.com on 30 Sep 2013 at 5:46
GoogleCodeExporter
commented
9 years ago Same problem as #10, essentially the same error. Testing on Chrome fully halted.
Chromedriver: 2.3
Chrome: 29.0.1547.76
Environment: Win7 x64, PHPUnit, Phing, Selenium standalone
===
PHPUnit_Extensions_Selenium2TestCase_WebDriverException: disconnected: unable
to send message to ren
derer
(Session info: chrome=29.0.1547.76)
(Driver info: chromedriver=2.3,platform=Windows NT 6.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 885 milliseconds
Build info: version: '2.35.0', revision: 'c916b9d', time: '2013-08-12 15:42:01'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
java.version: '1.7.0_21'
Session ID: cdd41af15df3ad89388e256fcc8c07a7
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true,
browserName=chrome, chrome=
{chromedriverVersion=2.3}, rotatable=false, locationContextEnabled=true,
version=29.0.1547.76, cssSe
lectorsEnabled=true, databaseEnabled=true, handlesAlerts=true,
browserConnectionEnabled=false, webSt
orageEnabled=true, nativeEvents=true, applicationCacheEnabled=false,
takesScreenshot=true}]Original comment by ellery.s...@gmail.com on 1 Oct 2013 at 6:00
GoogleCodeExporter
commented
9 years ago We started to see the "timed out receiving message from renderer" just
yesterday.
Chromedriver: 2.4
Chrome: 30 stable, 5 browser per node concurrently
Environment: Linux 3.5.0-23-generic x86, TestNG, Selenium 2.35 via GRID (and so
far only on the GRID)
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from
renderer: 2.150
(Session info: chrome=30.0.1599.66)
(Driver info: chromedriver=2.4.226074,platform=Linux 3.5.0-23-generic x86)
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 302.40 secondsOriginal comment by edw...@gmail.com on 4 Oct 2013 at 7:56
GoogleCodeExporter
commented
9 years ago We are running Selenium grid and our nodes were just recently updated to Chrome
30. We tried updating chromedriver to 2.4, but are now getting...
Caused by: org.openqa.selenium.TimeoutException: timeout: Timed out receiving
message from renderer: 10.000
(Session info: chrome=30.0.1599.69)
(Driver info: chromedriver=2.4.226107,platform=Windows NT 6.1 SP1 x86_64Original comment by harbe...@gmail.com on 7 Oct 2013 at 6:03
GoogleCodeExporter
commented
9 years ago org.openqa.selenium.WebDriverException: unknown error: unable to discover open
pages
(Driver info: chromedriver=2.4.226107,platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 22.46 seconds
System info: chrome=30.0.1599.101, os.name: 'Windows 7', os.arch: 'amd64',
os.version: '6.1', java.version: '1.7.0_21'Original comment by dr.x....@gmail.com on 21 Oct 2013 at 8:52
GoogleCodeExporter
commented
9 years ago Has anyone found a fix for this?
I agree with #3, since the chromeDriver update we get failures randomly all the
time now.
I was thinking of a 'try again' in the test since know one knows how to fix
this but it feels so wrong in doing that.
Original comment by kurt.har...@gmail.com on 25 Nov 2013 at 10:37
GoogleCodeExporter
commented
9 years ago [deleted comment]I am running chromedriver with 5 parallel thread.
I got "Timed out receiving message from renderer" error on each execution at
least for 5% of total tests. (With one thread it is ~0.5%)Original comment by kimiak2...@gmail.com on 26 Nov 2013 at 4:09
GoogleCodeExporter
commented
9 years ago having the same issue here, it's rly annoying for it's happening randomly, has
anyone figured out the cause fo this yet?Original comment by wyh.mich...@gmail.com on 11 Dec 2013 at 1:51
GoogleCodeExporter
commented
9 years ago btw, I'm using chrome=31.0.1650.63 and selenium 2.38.0 in grid modeOriginal comment by wyh.mich...@gmail.com on 11 Dec 2013 at 1:52
GoogleCodeExporter
commented
9 years ago I have the same issue. I upgraded to the latest stable chrome for linux (64)
and downloaded chromedriver 2.8.
Every once in a while click() POST request gets the error:
TimeoutException: Message: u'timeout: Timed out receiving message from
renderer: 496.356\n (Session info: chrome=31.0.1650.63)\n (Driver info:
chromedriver=2.8.240825,platform=Linux 3.5.0-23-generic x86_64)'
Original comment by micha...@adallom.com on 18 Dec 2013 at 2:53
GoogleCodeExporter
commented
9 years ago [deleted comment][deleted comment]I get this on windows machine too!
POST
http://....:4444/wd/hub/session/29a1c0f1-8922-4d8a-b799-a389e9e25194/element/2/c
lick {"sessionId": "29a1c0f1-8922-4d8a-b799-a389e9e25194", "id": "2"}
18:13:51.650 FAIL TimeoutException: Message: u"timeout: Timed out receiving
message from renderer: 489.057\n (Session info: chrome=31.0.1650.63)\n
(Driver info: chromedriver=2.7.236900,platform=Windows NT 6.1 SP1 x86_64)
(WARNING: The server did not provide any stacktrace information)\nCommand
duration or timeout: 500.80 seconds\nBuild info: version: '2.37.0', revision:
'a7c61cb', time: '2013-10-18 17:14:00'\nSystem info: host: 'AdallomWin7-VM',
ip: '....', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
java.version: '1.7.0_45'\nSession ID: 85a64c3769cd75c769bd8e7e0b35fcd1\nDriver
info: org.openqa.selenium.chrome.ChromeDriver\nCapabilities [{platform=XP,
acceptSslCerts=true, javascriptEnabled=true, browserName=chrome,
chrome={userDataDir=C:\\Users\\User\\AppData\\Local\\Temp\\scoped_dir9128_6985},
rotatable=false, locationContextEnabled=true, version=31.0.1650.63,
takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false,
handlesAlerts=true, browserConnectionEnabled=false, webStorageEnabled=true,
nativeEvents=true, applicationCacheEnabled=false, takesScreenshot=true}]" ;
Screenshot: available via screen ; Stacktrace:
at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (None:-2)
at sun.reflect.NativeConstructorAccessorImpl.newInstance (None:-1)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (None:-1)
at java.lang.reflect.Constructor.newInstance (None:-1)
at org.openqa.selenium.remote.ErrorHandler.createThrowable (ErrorHandler.java:193)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed (ErrorHandler.java:145)
at org.openqa.selenium.remote.RemoteWebDriver.execute (RemoteWebDriver.java:554)
at org.openqa.selenium.remote.RemoteWebElement.execute (RemoteWebElement.java:268)
at org.openqa.selenium.remote.RemoteWebElement.click (RemoteWebElement.java:79)
at sun.reflect.GeneratedMethodAccessor40.invoke (None:-1)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (None:-1)
at java.lang.reflect.Method.invoke (None:-1)
at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement$1.invoke (EventFiringWebDriver.java:327)
at com.sun.proxy.$Proxy3.click (None:-1)
at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.click (EventFiringWebDriver.java:340)
at sun.reflect.GeneratedMethodAccessor40.invoke (None:-1)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (None:-1)
at java.lang.reflect.Method.invoke (None:-1)
at org.openqa.selenium.remote.server.KnownElements$1.invoke (KnownElements.java:63)
at com.sun.proxy.$Proxy4.click (None:-1)
at org.openqa.selenium.remote.server.handler.ClickElement.call (ClickElement.java:29)
at org.openqa.selenium.remote.server.handler.ClickElement.call (ClickElement.java:1)
at java.util.concurrent.FutureTask.run (None:-1)
at org.openqa.selenium.remote.server.DefaultSession$1.run (DefaultSession.java:169)
at java.util.concurrent.ThreadPoolExecutor.runWorker (None:-1)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (None:-1)
at java.lang.Thread.run (None:-1) Original comment by micha...@adallom.com on 18 Dec 2013 at 4:29
GoogleCodeExporter
commented
9 years ago #20 and #23,
Would you mind sharing a test page and the test code to reproduce the problem?
Will the clicking closing a popup window?
It would be great if you could provide chromedriver.log with verbose logging
turned on. You may refer to
https://sites.google.com/a/chromium.org/chromedriver/logging on how to turn on
verbose logging.Original comment by st...@chromium.org on 26 Dec 2013 at 11:54
GoogleCodeExporter
commented
9 years ago Same problem as #10, occasionally webdriver hangs on page load
Chromedriver: 2.8
Chrome: 32.0.1700.76 m
Environment: Win8.1 x64, NUnit, Selenium Webdriver 2.39
I has this bug from I updated chrome to v.32.
In ChromeDdriver logs:
[68864.333][SEVERE]: Timed out receiving message from renderer: 296.040
[68874.337][SEVERE]: Timed out receiving message from renderer: 10.000
[69174.338][SEVERE]: Timed out receiving message from renderer: 300.000
[69184.339][SEVERE]: Timed out receiving message from renderer: 10.000
[69484.339][SEVERE]: Timed out receiving message from renderer: 300.000
[69494.340][SEVERE]: Timed out receiving message from renderer: 10.000Original comment by strycz...@gmail.com on 21 Jan 2014 at 8:07
GoogleCodeExporter
commented
9 years ago [deleted comment]Met the same issue since I updated my chromedriver to the latest version. The
page just hangs on to load and gives me a timeoutExcepetion. It stuck at
"driver.navigate().refresh()". Any idea about it? ThanksOriginal comment by manizhou...@gmail.com on 21 Jan 2014 at 3:51
GoogleCodeExporter
commented
9 years ago bug is very troublesome, any ideas to fix it ? :/Original comment by strycz...@gmail.com on 23 Jan 2014 at 7:39
GoogleCodeExporter
commented
9 years ago I met this issue when I was using driver.navigate().refresh. So have to find
another way to go to the page instead of using refresh() function, i.e.
re-navigate to the page by using url. Now my automation tool works properly.Original comment by manizhou...@gmail.com on 24 Jan 2014 at 12:32
GoogleCodeExporter
commented
9 years ago issue doesn't exist with chrome v.33 beta !Original comment by strycz...@gmail.com on 24 Jan 2014 at 6:19
GoogleCodeExporter
commented
9 years ago just update your selenium standalone server and drivers...Original comment by dariusga...@gmail.com on 24 Jan 2014 at 11:52
GoogleCodeExporter
commented
9 years ago I have chrome and driver updated:
failures tc: null org.openqa.selenium.TimeoutException: timeout: Timed out
receiving message from renderer: 1.005
(Session info: chrome=33.0.1750.70)
(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: 10.54 seconds
Build info: version: '2.39.0', revision:
'14fa800511cc5d66d426e08b0b2ab926c7ed7398', time: '2013-12-16 13:18:38'
System info: host: 'xxx', ip: 'xxx', os.name: 'Windows 8', os.arch: 'amd64',
os.version: '6.2', java.version: '1.7.0_25'
Session ID: bf2e9d01757631bcc4f1bb2ec3faae41
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=WIN8, acceptSslCerts=true, javascriptEnabled=true,
browserName=chrome,
chrome={userDataDir=C:\Users\xxx\AppData\Local\Temp\scoped_dir19276_17242},
rotatable=false, locationContextEnabled=true, version=33.0.1750.70,
takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false,
handlesAlerts=true, browserConnectionEnabled=false, nativeEvents=true,
webStorageEnabled=true, applicationCacheEnabled=false, takesScreenshot=true}]
:( :(
Original comment by jfernand...@gmail.com on 11 Feb 2014 at 9:08
GoogleCodeExporter
commented
9 years ago I got this error for the first time today too. A fix would be much appreciatedOriginal comment by owenflet...@gmail.com on 17 Feb 2014 at 8:49
GoogleCodeExporter
commented
9 years ago Would you please provide a test page and the test code to reproduce the problem?
And please follow https://sites.google.com/a/chromium.org/chromedriver/logging
to turn on verbose logging and attach chromedriver.log to your post.
Without these information, we might not be able to investigate further.Original comment by st...@chromium.org on 18 Feb 2014 at 8:29
GoogleCodeExporter
commented
9 years ago Hello everybody.
I am testing npApi extension with Selenium python library and chromedriver.
I open chrome, navigate to the test page. There is a script on the page which
opens pop-up window.
Then i call some plugin function which leads to executing javascript on the
pop-up page:
document.open();
document.write(...);
document.close();
After this i want to check that plugin have replaced pop-up window content, so
i call
wait.until(lambda driver: driver.find_element_by_css_selector(...))
After 10 min of waiting this code leads to error:
Message: u'timeout: Timed out receiving message from renderer: 600.000\n
(Session info: chrome=33.0.1750.146)\n (Driver info:
chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_64)'
I tried to create small python script to reproduce the problem but with no
luck. Error occures only when npApi plugin replaces page content.
I attached chromedriver.log
Original comment by WarmAndS...@gmail.com on 4 Mar 2014 at 10:03
Attachments:
GoogleCodeExporter
commented
9 years ago #35:
It seems you are hitting issue 450.Original comment by st...@chromium.org on 4 Mar 2014 at 5:42
GoogleCodeExporter
commented
9 years ago I am getting this issue too...anybody have any idea what is causing it?Original comment by owenflet...@gmail.com on 7 Apr 2014 at 8:19
GoogleCodeExporter
commented
9 years ago I am also having this issue with Chrome 34 and Chrome 35 on page load
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from
rendererOriginal comment by jselen...@gmail.com on 13 Jun 2014 at 4:34
GoogleCodeExporter
commented
9 years ago My contribution to this case is quite arbitrary, but had experienced some
consistently reoccurring race condition between the time a webdriver request is
in process and the secondary window closing. In my case, something was
triggering the error above while waiting for a window to close (and for an
OAuth transaction to complete)
I had to remove an offending line of code to avoid the issue related to
syncing. Now I cannot recall if the line I removed had to do with fetching
the window title, or something else relating to the wait. In this case you
may need to try relaxing some of your syncing code to avoid the error. Original comment by matt...@fullcontact.com on 13 Jun 2014 at 8:32
GoogleCodeExporter
commented
9 years ago Same here. I see the same error on a lot of my tests. Sometimes the error does
not show up on the exact same test. I am using Chrome 35.
Anyone have any workaround.Original comment by rafaf...@gmail.com on 14 Jun 2014 at 12:30
GoogleCodeExporter
commented
9 years ago Could someone please provide a reproducible testcase with a html test page?
Without such information, I'm afraid that we might not be able to investigate
the issue.Original comment by st...@chromium.org on 14 Jun 2014 at 1:38
GoogleCodeExporter
commented
9 years ago The problem vanished months ago for me. What I did was: remove all timeout
options whatsoever. Maybe that helps anyone...Original comment by stefango...@netzfrei.org on 15 Jun 2014 at 4:58
GoogleCodeExporter
commented
9 years ago [deleted comment][deleted comment][deleted comment][deleted comment]We started getting this issue a few months ago. We haven't tried removing the
timeout options (that may not work for us - we need adjusted values). We have a
JS-heavy app and it happens only sometimes, at unpredictable points during the
tests' execution, with no known reproduction path yet.
We do not have any third-party ads and this sometimes happens well after page
load and into test execution, i.e. the window "onload" handler has been called
so it's not as though the page is still waiting for something.
If we could provide a simple test page / test case that, in our environment,
reproduced the failure 1 out of N times, even if not every time, would that be
helpful? We don't have that yet, but may be able to get there with some effort.Original comment by g...@asana.com on 8 Jul 2014 at 6:08
GoogleCodeExporter
commented
9 years ago I am having this issue with Chrome 34 on page load. After the line 296, I got
errors:
296
self.webdriver.find_element_by_id('confirm-license-upload-again').click()
297 WebDriverWait(self.webdriver, 2400).until(lambda driver:
"Accepted file" in driver.page_source)
self.webdriver.find_element_by_id('confirm-license-upload-again').click()
File "/home/testenv/local/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py", line 60, in click
self._execute(Command.CLICK_ELEMENT)
File "/home/testenv/local/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py", line 370, in _execute
return self._parent.execute(command, params)
File "/home/testenv/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 166, in execute
self.error_handler.check_response(response)
File "/home/testenv/local/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py", line 164, in check_response
raise exception_class(message, screen, stacktrace)
TimeoutException: Message: u'timeout: Timed out receiving message from
renderer: 300.000\n (Session info: chrome=34.0.1847.116)\n (Driver info:
chromedriver=2.10.267518,platform=Linux 3.11.0-19-generic x86_64)'
Anyone can provide any workaround to bypass this issue? Original comment by lisatheo...@gmail.com on 13 Aug 2014 at 10:14
GoogleCodeExporter
commented
9 years ago We have a reproducible case, where if the client side js of the page makes a
request, and the TCP connection is immediately dropped (not sent an error, but
straight-out dropped) Chromedriver hangs with this error.Original comment by Jona...@gmail.com on 25 Aug 2014 at 6:01
GoogleCodeExporter
commented
9 years ago It seems error is still reproducible.
Doing:
http://localhost:9515/session/910b50437fe23aa64ef8dbae8bcd83eb/element/0.3717294
577509165-3/click
Opening a new page it returns:
{
sessionId: "910b50437fe23aa64ef8dbae8bcd83eb"
status: 21
value: {
message: "timeout: Timed out receiving message from renderer: 10.000 (Session
info: chrome=37.0.2062.102) (Driver info:
chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64)"
}-
}
But the issue was not present on Chrome 36 and appeared after update to Chrome
37
Original comment by vd.fall...@gmail.com on 29 Aug 2014 at 2:27
Original issue reported on code.google.com by
prasanna...@gmail.comon 24 Jun 2013 at 2:00