This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
browser.pause() crashes #1893
Comments
What's your version of node? |
node is v0.12.0 |
ah yes. So apparently node has changed their 'debugger' module several times since v0.10.30. Namely v0.10.31 causes significant delays when you use element explorer/pause (see #1890) The first issue I've filed a bug against node (again, see issue). The second issue, I am currently fixing; but even after I fix it, elementexplorer/pause is still unusable with the delay. The only workaround I can think of right now is use node 0.10.30 or earlier. |
Thanks for your help! Switching to node 0.10.30 works. |
👍 I was using .12 then had to revert to .10 for the same issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I seem to have protractor working fine, unless I use a browser.pause() statement. When it hits the pause, it tells me "Debugger listening on port 5858", but nothing after that. No debugger interface. And no commands work, although ^c quits the process. It does pause the Chrome browser, however it is blank, and in the address bar it says "data:,". I've also tried using Firefox, with the same result except the browser address bar is blank. I have the same problem using both mocha and jasmine.
I am running Mac OS 10.10.2, and protractor 1.8.0.
Here is my protractor.conf.js:
and my spec file
It runs fine if I comment out the browser.pause() line.
My output running protractor --troubleshoot is:
The text was updated successfully, but these errors were encountered: