PhantomJS 2 remote debugging is broken #12864

iradul · 2015-01-07T20:25:59Z

After running phantomjs with --remote-debugger-port=8080 and trying to debug with Google Chrome (Version 39.0.2171.95) "about:blank" link is missing. Also I tried to forcefully go to http://127.0.0.1:8080/webkit/inspector/inspector.html?page=1 but that produces empty page with no debugging capabilities.
Tested on Windows 7 with PhantomJS 2.0 built from source.

Pharb · 2015-01-08T13:52:48Z

The remote debugger works on Ubuntu with the latest PhantomJS master built from source, but the links to the webkit inspector are broken.

What's the HTML source of http://127.0.0.1:8080 ?

For me it's:

<html><head><title>Remote Web Inspector</title></head><body><ul>
<li><a href="/webkit/inspector/inspector.html?page=1"></li>
</ul></body></html>

The link http://localhost:8080/webkit/inspector/inspector.html?page=1 though works on Ubuntu, maybe it's more broken on Windows.

iradul · 2015-01-08T14:32:59Z

With http://127.0.0.1:8080 I'm getting exactly the same HTML source that you are getting.
But by following the link http://localhost:8080/webkit/inspector/inspector.html?page=1 browser is getting empty page with 404 status: HTTP/1.0 404 Not OK

vitallium · 2015-01-24T13:18:13Z

Confirmed.

vitallium · 2015-01-24T13:29:43Z

Fixed in #12899

Fixes #12864.

iradul · 2015-01-26T15:40:31Z

I don't think this is fixing the problem (tested in Windows only). Remote debugger inspector page still not shows about:blank link. This time opening http://127.0.0.1:8080/webkit/inspector/inspector.html?page=1 in Chrome will load inspector page, so no more 404 code, but debugging is still not working. You can't set proper breakpoints inside __run function (or you can but they are ignored), though you can execute script with __run() call from console. I also noticed that GUI is different from what we had in PhantomJS 1.9 (probably because of newer WebKit version).

iradul · 2015-01-27T17:34:04Z

This is workaround that works for me, in utils.cpp replace loadJSForDebug with this:

bool loadJSForDebug(const QString& jsFilePath, const QString &jsFileLanguage, const Encoding& jsFileEnc, const QString& libraryPath, QWebFrame* targetFrame, const bool autorun)
{
    QString scriptPath = findScript(jsFilePath, libraryPath);
    QString scriptBody = jsFromScriptFile(scriptPath, jsFileLanguage, jsFileEnc);

    if (!autorun) {
        scriptBody = "function __run() {\n" + scriptBody + "\n}";
    }

    targetFrame->evaluateJavaScript(scriptBody, QString("debugger"));

    return true;
}

Then while remote debugging there will be (no domain) item in Sources panel and inside of it will be debugger from where you can properly set breakpoints. Also for me this debugger page is accessible and can be seen only using arrow keys and not by mouse.
Side effect is that there is no more need for remote_debugger_harness.html resource.

vitallium · 2015-02-01T19:36:46Z

@iradul can you please show me a small example? In my case I can debug JS code (on Windows).

iradul · 2015-02-02T00:37:33Z

Using PhantomJS 2.0 binary built from source (remote debugging with binary from website doesn't work at all) and running remote debugger on this test.js script:

require('webpage').create().open('http://google.com', function() {
    console.log('ok!');
    phantom.exit();
});

phantomjs.exe --remote-debugger-port=8080 test.js

with Google Chrome I'm getting this:

Now if I open http://localhost:8080/webkit/inspector/inspector.html?page=1 manually see below:

I'm getting same behavior on 3 different Windows 7 machines.

They are already linked in QtWebkit on Linux/OS X. (See issue #12864 and #12899).

ariya · 2015-03-01T22:55:19Z

@vitallium With your check-in in 2.0 branch (to include Web Inspector resource, from around Jan 24), I assume this issue is fully addressed? If yes, then probably it's a good idea for us to roll out 2.0.1 with this fix.

vitallium · 2015-03-02T08:36:55Z

@ariya I can, but there are still a small bunch of issues, that I'd like to fix. I'll list them here #12970

ariya · 2015-03-05T05:21:18Z

@vitallium Those can still go to 2.1, don't they?

vitallium · 2015-03-05T14:00:42Z

@ariya I think so.

aschmalzhaf · 2015-05-06T08:08:01Z

Can anyone confirm that the changes done in February fix the reported issue?
PhantomJS is completely new to me, but when I did a build two days ago on Windows (branch 2.0 - I can see the changes) I still see the behavior described by iradul on Feb. 2nd in this thread.

Has anybody else tried to buld PhantomJS from sources - and saw a working debugger?

iradul · 2015-05-06T20:36:08Z

Issue is not completely fixed, as I explained here.

aschmalzhaf · 2015-05-06T22:00:15Z

@iradul, I asked because the fix was done on Feb 5th - your comment was written on Feb 2nd (see fix here: 8e8546b).
So I thought when I read the thread that it is actualy fixed (or: should be...).

Thanks for your statement here, again, that it isn't completely fixed.

LeMoussel · 2015-05-28T16:35:07Z

One idea when PhantomJS Release 2.0.1 will be available to download?

bedney · 2015-07-09T05:48:38Z

Still seeing the issues that @iradul was seeing on Feb 5th. Any ETA on 2.0.1?

Issue: ariya#12864

@iradul

As @iradul suggested, simplify resource loading in remote debug mode. After this change we don't need remote_debugger_harness.html anymore. And breakpoints will work now again. Issue ariya#12864

iradul · 2017-02-08T21:24:19Z

You should not use --remote-debugger-autorun=true
With that option on phantom will immediately execute __run() internally so while you're loading localhost:9000 into Chrome your phantom script probably already ended.

scottgrohusky · 2017-02-08T23:04:55Z

I think this is a dupe issue which is open.

I ran:

phantomjs --remote-debugger-port=9000 practice2/chapter01/recipe08.js

and

phantomjs --remote-debugger-port=9000 --proxy-type=none practice2/chapter01/recipe08.js

Breakpoints are still not being hit and __run() does not output anything.

sontek · 2017-02-14T05:29:32Z

I'm seeing the same thing, the console doesn't actually run the __run() command, it inserts a newline in Chrome. The console doesn't work at all in Firefox. It works perfectly in safari though.

jesobreira · 2017-02-16T05:02:30Z

Same issue. __run() + enter just adds a line feed on the console window and I am unable to get it running. Chrome on Ubuntu 16.10.

wgiroir · 2017-02-17T16:45:53Z

I have also verified that this failed on using Chrome and Firefox but works with Safari

jesobreira · 2017-02-17T16:53:57Z

@wgiroir what OS are you using? I couldn't get it working on Safari on Win7.

sontek · 2017-02-17T16:56:13Z

I'm safari + OSX

wgiroir · 2017-02-21T14:40:38Z

I was running Safari on OSX and phantomjs on CentOS 7

jesobreira · 2017-02-21T17:59:24Z

I could run the debug using a very old Chrome version (Chrome 17) that I download here (run sandboxie-d as I can't confirm the procedence of it, although it worked with me - do not use it for browsing, use it for debugging your PhantomJS scripts only).

Galleleo · 2017-03-17T12:11:02Z

Arora works for me! It's a browser based on Qt and WebKit and displays pages like Safari does. I tried Chrome on Ubuntu 16.10 as well as Safari 5.0.5 in Wine but Arora is (so far) the only browser that executes __run()

lewsid · 2017-03-23T17:47:43Z

Any word on this? I'm running PhantomJS 2.1.1 on OSX and the debugger simply doesn't work in any browser I try. I get the same thing others have reported: Entering the __run() command returns nothing, and no breakpoints are ever hit.

lewsid · 2017-03-24T15:32:44Z

For those like me still having trouble, I've found that using an old version of Chromium works well, if your default browser is Chrome. Here's a link to a 2014 build of Chromium that I've had luck getting to work with PhantomJS's remote debugger: https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Mac%2F280075%2Fchrome-mac.zip?generation=1409176787550000&alt=media

jumoreno · 2017-03-29T17:03:27Z

@lewisd, I can confirm I can get chrome debugger to work in the old Chromium version. Will try and understand why this is and post on here if I find anything. I have been looking for other remote debugging breakpoint options for casperjs and will post here if I find anything that works as well. Seems like we need to add support for latest Chrome though.

iradul · 2017-03-29T17:44:07Z

For those who use Code editor, you can use PhantomJS debugger extension.

twalpole · 2017-03-29T18:02:30Z

This is because the protocol used by Chrome changed after the Webkit- Blink engine split.

lewsid · 2017-03-29T18:26:49Z

This issue should be re-opened, no?

jumoreno · 2017-03-29T20:53:09Z

@iradul thanks for the heads up on the Code editor debugger extension -> do you happen to know runtime configuration required for a Mac? Took a quick look here so far and played a bit with it but no success so far.

iradul · 2017-03-31T15:13:39Z

@jumoreno, hmm never tested on Mac but should be straight forward if you follow steps from documentation, check those out:
https://marketplace.visualstudio.com/items?itemName=iradul.debugger-for-phantomjs
https://github.com/iradul/vscode-phantomjs-debug (raise an issue if needed)

twalpole · 2017-03-31T17:49:56Z

@jumoreno Also on a Mac it should work using Safari since IIRC it still uses the same protocol (WebKit based)

thorn0 · 2017-04-12T23:43:15Z

This must help: node-inspector/node-inspector#951 (comment)

mingjunz · 2017-10-29T05:46:05Z

anyone have workaround for this problem?

BlackZork · 2017-11-02T13:22:28Z

@mingjunz, two workrounds:

Use Chromium 50.x
Try Tizen Console Fix extension for Chrome.

stale · 2019-12-28T18:55:23Z

Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed. In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!

brittotprince · 2021-05-21T13:00:58Z

I had the same issue and was having a hard time finding chrome 50.x
Attaching the link below for future use
Chrome version: 50.0.2657.12:

Disclaimer: The below project helped me get this easily. Utilize it in case you need any other version of chrome.
https://vikyd.github.io/download-chromium-history-version/#/

vitallium self-assigned this Jan 24, 2015

vitallium mentioned this issue Jan 24, 2015

Include Web Inspector resources. #12899

Closed

vitallium added this to the Release 2.0 milestone Jan 24, 2015

ariya added the Regression label Jan 24, 2015

ariya modified the milestones: Release 2.0.1, Release 2.0 Jan 24, 2015

vitallium added a commit that referenced this issue Jan 24, 2015

Include Web Inspector resources.

2a6c6af

Fixes #12864.

ariya added a commit that referenced this issue Feb 5, 2015

Issue ##12864: Fix Windows build (from Vitaly).

8e8546b

vitallium added a commit that referenced this issue Feb 7, 2015

Don't include inspector resources.

26ed336

They are already linked in QtWebkit on Linux/OS X. (See issue #12864 and #12899).

sfsr12 mentioned this issue Jul 21, 2015

Incorrect cursor position in remote debugging #13427

Closed

vitallium mentioned this issue Aug 3, 2015

2.0 release running remote-debugger on win7 always comes up with 404 #13455

Closed

vitallium added a commit to vitallium/phantomjs that referenced this issue Aug 3, 2015

Include Web Inspector resources in Windows build

dcf1e9d

Issue: ariya#12864

vitallium reopened this Mar 29, 2017

vitallium removed the In progress label Mar 29, 2017

ghost removed the 2.0 Regression label Jan 10, 2018

ghost removed this from the Release 2.1 milestone Jan 10, 2018

stale bot added the stale label Dec 25, 2019

stale bot closed this as completed Dec 28, 2019

PhantomJS 2 remote debugging is broken #12864

PhantomJS 2 remote debugging is broken #12864

Comments

iradul commented Jan 7, 2015

Pharb commented Jan 8, 2015

iradul commented Jan 8, 2015

vitallium commented Jan 24, 2015

vitallium commented Jan 24, 2015

iradul commented Jan 26, 2015

iradul commented Jan 27, 2015

vitallium commented Feb 1, 2015

iradul commented Feb 2, 2015

ariya commented Mar 1, 2015

vitallium commented Mar 2, 2015

ariya commented Mar 5, 2015

vitallium commented Mar 5, 2015

aschmalzhaf commented May 6, 2015

iradul commented May 6, 2015

aschmalzhaf commented May 6, 2015

LeMoussel commented May 28, 2015

bedney commented Jul 9, 2015

iradul commented Feb 8, 2017

scottgrohusky commented Feb 8, 2017

sontek commented Feb 14, 2017

jesobreira commented Feb 16, 2017

wgiroir commented Feb 17, 2017

jesobreira commented Feb 17, 2017

sontek commented Feb 17, 2017

wgiroir commented Feb 21, 2017

jesobreira commented Feb 21, 2017

Galleleo commented Mar 17, 2017

lewsid commented Mar 23, 2017

lewsid commented Mar 24, 2017

jumoreno commented Mar 29, 2017

iradul commented Mar 29, 2017

twalpole commented Mar 29, 2017

lewsid commented Mar 29, 2017

jumoreno commented Mar 29, 2017

iradul commented Mar 31, 2017 • edited Loading

twalpole commented Mar 31, 2017

thorn0 commented Apr 12, 2017

mingjunz commented Oct 29, 2017

BlackZork commented Nov 2, 2017

stale bot commented Dec 28, 2019

brittotprince commented May 21, 2021 • edited Loading

iradul commented Mar 31, 2017 •

edited

Loading

brittotprince commented May 21, 2021 •

edited

Loading