Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Element explorer hangs in protractor >=1.7 if you have node >=0.10.31 #1890

Closed
hankduan opened this issue Mar 3, 2015 · 6 comments
Closed

Comments

@hankduan
Copy link
Contributor

hankduan commented Mar 3, 2015

Element explorer hangs in versions 1.7 or later.

NOTE: this behavior only appears if you are on node version 0.10.31 or above

Under closer look, you should see that this delay is not indeterministic. To be exactly:
if you wait n seconds to enter a command, the delay will be (n + time to execute command) seconds.
In other words, if you execute a simple command like var x = 3, which takes no time to execute, the delay is equal to the amount of time you waited before entering the command.

Try this:

$ //start element explorer
> var x = 3  //should return immediately
> // now wait 10 seconds, and then type `var x = 3`
> // should wait ~10s before returning. 

An issue has been filed with additional information here: nodejs/node-v0.x-archive#9333

@hankduan hankduan changed the title Element explorer hangs in versions 1.7 and above Element explorer hangs in protractor >=1.7 if you have node >=0.10.31 Mar 4, 2015
@hankduan
Copy link
Contributor Author

hankduan commented Mar 5, 2015

FYI: The only workaround for this issue right now is either:

  1. downgrade protractor to 1.6.1
    or
  2. use node.js to 0.10.30 or lower.

@shattenjager
Copy link

I tried to downgrade to 0.10.29 but still is not working. I get SyntaxError: evalmachine.:1 on my Win machine. I also tried to install an older version of Protractor but I don't know how, since I use npm. My current version is 2.1.0. Also I get this error not using elementExplorer but the debug mode triggered by a browser.pause() method in my code, then I used "repl" to switch to the interactive mode; from there I can do only a browser.get() but can't manage to interact with any element.
image

Win 8.1 64
node 0.12.4
npm 2.10.1
protractor 2.1.0

@juliemr
Copy link
Member

juliemr commented May 28, 2015

@shattenjager you do have a syntax error, you're missing a ) closing the element call.

I'm not sure why your error message is so bad, that seems like something to do with how node interacts with windows. On mac, it prompts you to continue the input, since the parentheses haven't been matched.

@shattenjager
Copy link

Geez, thanks, I feel dumb, I apologize!!

@hankduan
Copy link
Contributor Author

fyi: This will be fixed when node 0.12.5 gets released. nodejs/node-v0.x-archive#9333 (comment).

@juliemr
Copy link
Member

juliemr commented Sep 30, 2015

Node 0.12.5 is out, woo! Closing.

@juliemr juliemr closed this as completed Sep 30, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants