protractor: Element Explorer totally unresponsive

Node Version: 7.4.0
Protractor Version: 5.0.0
Browser: Chrome
OS: Windows 7 64bit

I’m following the guide here for setting up a REPL, which says to run protractor thusly: protractor --elementExplorer. I do this, it launches a Chrome window, shows output in the console that suggests everything worked (e.g. “server started…”, “debugger listening…”), and leaves me at a prompt (>).

Nothing I type in this prompt produces any effect/response at all. I tried the examples given, such as browser.get('http://www.angularjs.org'), but pressing ENTER simple adds a carriage return to the screen and nothing else. I can keep hitting ENTER and the cursor keeps dropping down a line, but there is no response from protractor, nothing happens in the browser, etc. The only thing that produces a response is CTRL+C or CTRL+D, which serve to let me know the process is still running but that’s about it.

protractor-element-explorer

Note, if I keep trying to enter commands (they just pile up with no response), I eventually get this:

(node:3012) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 break listeners added. Use emitter.setMaxListeners() to increase limit

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 11
Comments: 32 (11 by maintainers)

Commits related to this issue

fix(elementexplorer): Set script breakpoints with cross-platform safe paths. Fixes #4011 — committed to heathkit/protractor by heathkit 7 years ago
fix(elementexplorer): Set script breakpoints with cross-platform safe paths. Fixes #4011 — committed to heathkit/protractor by heathkit 7 years ago
fix(elementexplorer): Set script breakpoints with cross-platform safe paths. Fixes #4011 — committed to heathkit/protractor by heathkit 7 years ago
fix(elementexplorer): Set script breakpoints with cross-platform safe paths. Fixes #4011 — committed to angular/protractor by heathkit 7 years ago

Most upvoted comments

Thanks @seanmay, yeah I think that’ll do it. I still want to understand element explorer a little bit better and where these paths originally came from, but I’ll probably end up doing a fix like that.

Thanks for your patience everyone! We’re planning on doing a 5.1.2 release tomorrow, and the fix for this should be included.

heathkit on May 8, 2017

Ok, @seanmay, I finally found it … debuggerCommons contains this function:

exports.setEvaluateBreakpoint = function(client, cb) {
  client.setBreakpoint({
    type: 'scriptRegExp',
    target: 'built/breakpointhook\.js', //jshint ignore:line
    line: 2
  }, function(err, response) {
    if (err) {
      throw new Error(err);
    }
    cb(response.breakpoint);
  });
};

Unfortunately the regex for the script doesn’t work on windows … removing ‘built/’ makes elementExplorer work as expected!

woppa684 on May 3, 2017