navigate_to sometimes fails with timeout error

[jvoegele]

We are using Hound with chrome_driver, and many of our feature tests fail due to calls to navigate_to returning {:error, :timeout}.

By watching the Chrome window that Hound is driving, I can see that the navigate_to calls are actually resulting in the correct page being loaded in the browser, but it seems that Hound is not receiving a response (from either Hackney or ChromeDriver) indicating successful page load, so the call eventually results in the timeout error. However, if I manually reload the page in the Chrome window (or just hit enter when the focus is on the Chrome address bar), then that suddenly causes a response to be sent back to Hound and the navigate_to function then returns normally (with a nil result).

I have attached the log output from ChromeDriver. The log output for the relevant navigate_to call begins on line 2460, and extends to line 2852. If I do nothing, then that is where the log output ends and I receive a timeout error from Hound. If I reload the page in the Chrome window, however, then I get the DEVTOOLS RESPONSE beginning on line 2853, and the navigate_to call returns successfully.

chromedriver.log

[garretttaco]

@jvoegele I am having the same issue. Did you happen to make any headway on solving this issue?

[abhishekbose87]

Hey guys !! Were you able to figure out a solution for this error ?

[jvoegele]

No luck here. Our feature tests continue to fail due to this error, so we have just disabled them for the time being.