Issue metadata
Sign in to add a comment
|
Receiving intermittent error: Timed out receiving message from renderer
Reported by
brandon....@gesture.com,
Jan 25 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: Unfortunately, this bug is intermittent. I have not been able to find any test or list of steps that consistently cause the issue to present itself. What is the expected behavior? What went wrong? When running Selenium tests using the new version of Chrome (64.0.3282) and the new Chromedriver (2.35), we are intermittently receiving this error: "Timed out receiving message from renderer: 600.000". This seems to be happening with approximately 1 in 100 tests, and they are always different tests that fail. This started occurring immediately after updating from Chrome v63 to Chrome v64. Did this work before? Yes 63.0.3239 Chrome version: 64.0.3282.119 Channel: stable OS Version: Ubuntu 14.04 Flash Version:
,
Jan 26 2018
Update 2: The issue is back! With the --disable-gpu attribute set, the problem seems less frequent, but I'm still getting the issue at least 4 or 5 times with every 2000-test run.
,
Jan 29 2018
,
Jan 29 2018
Adding TE-NeedsTriageHelp label as this issue seems to be out of TE scope and is related to Selenium tests and web driver. Tentatively adding Tests>WebDriver label. Could someone from dev team please have a look at this issue.
,
Jun 6 2018
Is this issue still occurring with the latest version of Chrome? If yes, could you provide ChromeDriver verbose log from a failed test?
,
Jun 30 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by brandon....@gesture.com
, Jan 25 2018