IE stability issue - occasional Javascript errors

[juliemr]

Example:

     UnknownError: JavaScript error (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 129 milliseconds
Build info: version: '2.41.0', revision: '3192d8a', time: '2014-03-27 17:17:32'
System info: host: 'WIN-8LIIH1BGM1D', ip: '172.20.42.188', os.name: 'Windows Server 2008 R2', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_38'
Session ID: ce12158e-4456-4529-8cc9-b8171739c296
Driver info: org.openqa.selenium.ie.InternetExplorerDriver
Capabilities [{platform=WINDOWS, elementScrollBehavior=0, javascriptEnabled=true, enablePersistentHover=true, ignoreZoomSetting=false, browserName=internet explorer, enableElementCacheCleanup=true, unexpectedAlertBehaviour=dismiss, version=11, cssSelectorsEnabled=true, ignoreProtectedModeSettings=false, requireWindowFocus=false, allowAsynchronousJavaScript=false, initialBrowserUrl=, handlesAlerts=true, nativeEvents=true, takesScreenshot=true}]
   Stacktrace:
     UnknownError: JavaScript error (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 129 milliseconds
Build info: version: '2.41.0', revision: '3192d8a', time: '2014-03-27 17:17:32'
System info: host: 'WIN-8LIIH1BGM1D', ip: '172.20.42.188', os.name: 'Windows Server 2008 R2', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_38'
Session ID: ce12158e-4456-4529-8cc9-b8171739c296
Driver info: org.openqa.selenium.ie.InternetExplorerDriver
Capabilities [{platform=WINDOWS, elementScrollBehavior=0, javascriptEnabled=true, enablePersistentHover=true, ignoreZoomSetting=false, browserName=internet explorer, enableElementCacheCleanup=true, unexpectedAlertBehaviour=dismiss, version=11, cssSelectorsEnabled=true, ignoreProtectedModeSettings=false, requireWindowFocus=false, allowAsynchronousJavaScript=false, initialBrowserUrl=, handlesAlerts=true, nativeEvents=true, takesScreenshot=true}]
==== async task ====
WebDriver.executeScript()
==== async task ====
Timed out waiting for page to load
    at null.<anonymous> (/Users/ralphj/protractor/spec/basic/findelements_spec.js:580:13)
==== async task ====
Asynchronous test function: it()
Error
    at verifyMethodsAdded (/Users/ralphj/protractor/spec/basic/findelements_spec.js:575:3)
    at Object.<anonymous> (/Users/ralphj/protractor/spec/basic/findelements_spec.js:462:1)

These happen during the wait for the page to load about 1% of the time.

[elgalu]

Did you try increasing browser.manage().timeouts().pageLoadTimeout(40000);

[juliemr]

Yeah, it's interesting that it's not actually failing the timeout for the wait. The actual code being executed in the browser (return window.location.href) is causing an error. If an error occurs during a webdriver.wait, it's propagated.

[juliemr]

More logs - https://gist.github.com/juliemr/ca0abc6b2b9416ea8273

[elgalu]

Weird, you get 9 ~ 10 failures on IE11 / IE10
When I run IE11 on a close Windows 8.1 laptop i only get failures related to getCurrentUrl()
https://gist.github.com/elgalu/5569c2eb6da599cfcd63

[juliemr]

Thanks for more data!

Capturing the error I often get:

{ stack: null,
  description: '\'window\' is undefined',
  number: -2146823279 }

EDIT - this doesn't seem to be the common cause

[juliemr]

Tried with windows 8 on saucelabs, didn't help. I didn't see the window is undefined error anymore, but the same end result.

[juliemr]

Live errors now out on Travis - https://travis-ci.org/angular/protractor/jobs/25825485

[juliemr]

Tentatively closing after 0500b2c. Please comment or open a new issue if something like this crops up again!

[fakewaffle]

I'm randomly getting the same type of timeouts with Browser Stack.

[fakewaffle]

I should add:

$ protractor --version
Version 1.1.1

https://gist.github.com/fakewaffle/f3b2ea0401ab815c27db
https://gist.github.com/fakewaffle/4a5fd49bdfe38cd4927f

[elgalu]

@fakewaffle, same tests always pass in Chrome-BrowserStack* right?

[fakewaffle]

Yes, and Firefox. IE is hit or miss.

[DylanLacey]

I'm seeing similar errors, but on execute_async Selenium commands in IE. The weird thing is, digging through the IEDriver source shows that these timeouts are occurring in the browser, not in the Selenium stack. The only two causes I could think of were that either IEDriver is completely ignoring the timeouts requested by users (Causing scripts to timeout almost immediately) or the browser is having timekeeping problems.

@fakewaffle Were your failing IE tests on BrowserStack? It'd be good to eliminate emulation problems from the equation (I'm seeing these errors on Sauce Labs).

[kaililleby]

I'm getting err.code 17 on windows 10 / explorer 11 - seemingly the same cause? The messages logged are the same as described in this issue.. should if (err.code == 13) be changed to if (err.code == 13 || err.code == 17) ?

[yimothy]

This error occurs almost 100% of the time in IE11 when there are adjacent browser.get() calls. See #4268.

It seems like the Javascript error does not get ignored in this case. A quick solution for this is to just use browser.driver.get() instead of the browser.get().