Protractor: sendKeys is very slow in IE 11

Created on 7 Nov 2014  Â·  18Comments  Â·  Source: angular/protractor

Hi All,

FYI recently my IE got upgraded to IE 11 and when I recently run the scripts it is executing very very slow.... Do anyone have faced the same problem. Do let me know.

The login page is taking nearly 2 sec for each character to enter in the text field.

Thanks,
Santhosh Chunchu

IE webdriver-manager external bug filed

Most helpful comment

Finally after 2 years it got closed :) Happy holiday to all :)

All 18 comments

Looks like this is the same issue: https://code.google.com/p/selenium/issues/detail?id=5116

Summary: It's probably the 64bit version of IEDriver.

We should consider changing webdriver-manager to only use the 32 bit version since this makes 64 pretty unusable.

@juliemr - Changed to 32 bit IE driver and all works good. Thanks

How do you change to the 32 bit IE Driver when using Webdriver-manager?

@dpaquette I've been struggling with the same this week, here's what I found:

The Webdriver-manager asks Node to provide the system architecture through an 'os.arch()' call, and chooses the URL accordingly. https://github.com/angular/protractor/blob/master/bin/webdriver-manager#L73

There isn't currently a way to pass in a configuration, but there's an open feature request here #1297

Node actually doesn't report the OS architecture on 'os.arch()', but whether or not the current process is 32-bit or 64-bit: https://github.com/joyent/node/issues/2862 I've confirmed it using Node v0.12.5, but this issue is three years old so it's apparently been that way for awhile.

As a workaround, if you're running the 32-bit version of node instead of the 64-bit version, then the Webdriver-manager will resolve the 32-bit version of the IE driver. Note: On Windows you may want to make sure your path is pointing to the correct 32-bit version of node (e.g. c:\program files (x86)\nodejs).

Hope it helps.

@codecadwallader I managed to get another workaround working for me yesterday. I manually downloaded the 32-bit copy of IEWebDriverServer and overwrote the file in C:\Users\myusername\AppData\Roaming\npmnode_modules\protractor\selenium. The catch was that I had to download the same version as the one that was previously installed (in my case 2.45).

Download the 32bit IEdriver and use it insted of the 64 bit

Even 32bit IEDriver gets slower.

Just to help anyone else that ends up here after hours of searching.

Install 32bit IE Driver

webdriver-manager update --ie32

Start Protractor with the 32bit IE Driver

_(if you are running 64bit os you must add switch or it will try to load 64bit driver)_

webdriver-manager start --ie32

@cnishina do you think we should default to the ie32 for webdriver-manager?

This still seems to be an issue. I tried the webdriver-manager start --32 and it is still very slow.

32Bit IE driver solves this problem.
For those who are searching for the drivers, link is here

Use in protractor conf like below:
exports.config = {
seleniumArgs: ['-Dwebdriver.ie.driver=node_modules/protractor/selenium/IEDriverServer.exe']
}

After responding to #1999, I think we should just default to ie32 and not bother with the x64 version of IEDriver.

So the following will by default download / start the 32-bit version:

webdriver-manager update --ie
webdriver-manager update --ie32
webdriver-manager start --ie
webdriver-manager start --ie32

If someone really needs the x64 version, we'll have add a flag:

webdriver-manager update --ie64
webdriver-manager start --ie64

In the help option, I'll also add that the x64 version has been known to be flaky.

Finally after 2 years it got closed :) Happy holiday to all :)

i used ie32 driver and my login page is in frame ,when i tried to run the script ,it is unable to locate my frame using ie32 driver
and same script is working fine with ie64 and its easily handling frame.(but it is type slow as character wise)

Any solution?

Try to update ie32 bit, webdriver-manager update --ie32. And then start the server.

Also ask debug questions in stack overflow.

Micromax
On Oct 12, 2016 8:31 PM, AdamRzymowski notifications@github.com wrote:
>

This still seems to be an issue. I tried the webdriver-manager start --32 and it is still very slow.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The same issue for me. The --ie32 runs IEDriver 32, but it doesn't resolve the issue of low performance of sendKeys(). Any thoughts?

image

Another option:

capabilities: {
    'browserName': 'internet explorer',
    'requireWindowFocus': true,
    'ignoreProtectedModeSettings': true
},

OR

multiCapabilities: [
     {
        'browserName': 'internet explorer',
         'requireWindowFocus': true,
         'ignoreProtectedModeSettings': true
      },
      {
        //  ...
      }
],

Source.

Was this page helpful?
0 / 5 - 0 ratings