New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 17 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment
link

Issue 883481: Breakpoints on remote debugging session not working

Reported by jesseg...@gmail.com, Sep 12

Issue description

Chrome Version       : 69.0.3497.92
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested: N/A

What steps will reproduce the problem?
1. Start simple node http server on remote host with --inspect option. In my case, the remote host was an Ubuntu server with IP address 192.168.100.24:

 $> node --inspect=192.168.100.24 server.js
 Debugger listening on ws://192.168.100.24:9229/[uid]

2. On windows box, attach debugger by opening up page with the following url:

 chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=192.168.100.24:9229/[uid]

3. In the sources tab, open up server.js and set breakpoint.

4. In a new browser tab, navigate to http://192.168.100.24:8080/

What is the expected result?

 The debugger breaks at breakpoint.

What happens instead of that?

 The http request completes without breaking in the debugger.

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Remote breakpoints worked prior to the Chrome update I received on 9/12. 

I've attached a screenshot of the debugger plus the 4 line server.js file I used to reproduce the problem.
 
debugger.jpg
151 KB View Download
debug-issue.tar
10.0 KB Download

Comment 1 by ajha@chromium.org, Sep 13

Components: Platform>DevTools
Labels: Needs-Triage-M69

Comment 2 by adr...@onezerohosting.com, Sep 13

Please fix this.  I can't roll back to a previous version of Chrome and yes, breakpoints do not work.

Comment 3 by adr...@onezerohosting.com, Sep 14

Bump

Comment 4 by adr...@onezerohosting.com, Sep 15

Heads up to those who are running into the same problem.  An alternative route is to use a different Chromium browser: https://www.makeuseof.com/tag/alternative-chromium-browsers/

I am using Vivaldi with the NiM Chrome extension and breakpoints are working just fine.

https://june07.com/nim

Comment 5 by alph@chromium.org, Sep 21

Components: -Platform>DevTools Platform>DevTools>JavaScript
Owner: kozy@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 6 by kozy@chromium.org, Sep 25

Cc: kozy@chromium.org eostroukhov@chromium.org
 Issue 844070  has been merged into this issue.

Comment 7 by kozy@chromium.org, Sep 25

 Issue 841697  has been merged into this issue.

Comment 8 by kozy@chromium.org, Sep 26

 Issue 851853  has been merged into this issue.

Comment 9 by 6...@onezerohosting.com, Oct 5

You can now change DevTools versions using NiM version 1.0.0

https://youtu.be/hjf6esnqOJQ

So an alternate browser is not needed as changing the default DevTools version will fix the current issue with Chrome.

Comment 10 by joshoooa...@gmail.com, Oct 12

With the latest Chrome 69, my NiM was no longer attaching dev tools to my node server... Eg none of my server files appeared in Sources.

Following the youtube link fixed that problem - now node reports "Debugger attached" and my server code appears in Sources, but now breakpoints are not stopping again.

@6...@onezerohosting.com what exactly should I have in the DevTools Version (custom): string to make it work?  I'm using "chrome-devtools://devtools/bundled/js_app.html" (from the video).

Comment 11 by joshoooa...@gmail.com, Oct 12

Hang on... I noticed that the URL node reports when the debugger connects works:

To start debugging, open the following URL in Chrome:
chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284981/inspector.html?experiments=true&v8only=true&ws=XXX.XXX.XXX.XXX:9229/87cc6788-50c8-4ac7-80ab-61cdb3946cab

And debugging works too with this URL!  

So I put this into the custom: field in NiM: 

chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284981/inspector.html

Works too!

Comment 12 by stephan....@gmail.com, Oct 12

Unfortunately, the "chrome-devtools://devtools/remote/serve_file" url returns a "HTTP/1.1 404 Not Found" page here.

And the "chrome-devtools://devtools/bundled/inspector.html?" url shows the sources, but doesn't let me hit any breakpoints.


Chrome: 69.0.3497.100 (64-bits)
NiM: 1.1.0
Windows: 10 (1803, build 17134.345)

Comment 13 by joshoooa...@gmail.com, Oct 12

@stephan....@gmail.com you need that full URL with the @... bit (and the @... bit will be based on your own environment): 

chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284981/inspector.html

I don't know how often that @60cd6e859b9f557d2312f5bf532f6aec5f284981 bit changes. If it changes often, it will take away much of the NiM convenience.

Comment 14 by kozy@chromium.org, Oct 12

Could someone try dedicated frontend (or chrome://inspect) in latest Google Chrome Canary on Mac or Windows (version 71) with latest Node 10.12? We merged some fixes to our frontend and to Node by itself and I hope that it should help.

Comment 15 by adr...@onezerohosting.com, Oct 12

Using the NiM "appspot" option (under options) works for me in all cases:

https://chrome-devtools-frontend.appspot.com/serve_file/@a10b9cedb40738cb152f8148ddab4891df876959/inspector.html

Comment 16 by kozy@chromium.org, Oct 14

It is amazing that NiM can resolve this problem but it achieves it by running old DevTools frontend, this solution won't help with fixing the root of this issue and do not allow to use a lot of new nice DevTools features, e.g. live evaluation in console.
Please let's focus on fixing DevTools, I believe that dedicated frontend from latest Google Chrome Canary with latest Node 10.x release should work with any kind of remote debugging sessions.
I am going to test new frontend against Node 8 on Windows at the beginning of next week as soon as I get access to windows machine.

Comment 17 by brucej...@gmail.com, Oct 14

I verified that canary fixes the debugging issue for node v8 & node v10.
see: https://github.com/ChromeDevTools/devtools-protocol/issues/103#issuecomment-429649817

Comment 18 by 6...@onezerohosting.com, Oct 15

Actually updated NiM (1.2.0) to use the most up to date version of DevTools (Chrome 71) as the default "appspot" as well as adding info on how to better use the custom setting https://june07.com/blog/nim-custom-devtools-url.

So all of the nice DevTools features are available via NiM and with all versions of Chrome (and Chromium based browsers), not just Chrome Canary.  This was previously the case if using the appropriate URL in the custom setting, but now it's the default "appspot" option.

Glad to hear the Canary version is working now!

Comment 19 by jesseg...@gmail.com, Oct 15

I also verified that remote breakpoints are working on version 71.0.3573.0 (Chrome Dev on windows) with both node 8.11.3 and 10.12.0. Thanks.

Comment 20 by gautham....@gmail.com, Oct 23

I've verified that the breakpoints work fine in 
Chrome 69.0.3497.100
Windows 10 Home (64-bit)
NodeJS v8.12.0

Comment 21 by kozy@chromium.org, Nov 5

Cc: l...@chromium.org alph@chromium.org dgozman@chromium.org
 Issue 901731  has been merged into this issue.

Comment 22 by brucej...@gmail.com, Dec 16

I verified that released build: Version 71.0.3578.80 (Official Build) (64-bit) repairs this issue.  All working now.

Comment 23 by alph@chromium.org, Dec 17

Status: Fixed (was: Assigned)
@brucejo75 Thank you for feedback. I'll close the bug.

Sign in to add a comment