Issue metadata
Sign in to add a comment
|
Breakpoints stopped working for Dev Tools - Node.js inspection on Windows
Reported by
brucej...@gmail.com,
May 17 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: Environment: Windows 10 Node 8.11.1 running node on Ubuntu within Windows Subsystem for Linux (WSL) 1. Create a node application. 2. run node with --inspect flag 3. putting debugger statements in code works, breakpoints can be placed in the code but the debugger does not break at the breakpoint. What is the expected behavior? Expected Node app to break on breakpoints What went wrong? File runs, but dev tools do not stop on the breakpoint Did this work before? Yes Version 65.0.3325.181 Chrome version: 66.0.3359.139 Channel: stable OS Version: 10.0 Flash Version: I noticed an issue in the Network tab of Developer Tools - Node.js. I attached 2 pictures showing the issue. v66 chrome debugger broken.png: 1. There is a path to the running node file displayed with a gear icon. 2. When I hover over the file:// folder it shows a path that is prepended with the path to the running node file. This is not a good path. 3. I can get bad paths when hovering over any of the files/folders. v65 chrome debugger working.png: 1. no path displayed 2. when hovering over files/folders I see no prepended path to the running node file. May be related to: https://bugs.chromium.org/p/chromium/issues/detail?id=820728
,
May 21 2018
@lushnikov - were there any changes that might've broken this?
,
May 21 2018
I have the same problem, it doesn't stop at the breakpoint selected.
,
May 23 2018
Perhaps similar to this issue? https://bugs.chromium.org/p/chromium/issues/detail?id=838891
,
May 23 2018
Looks like this also affect OSX: https://github.com/meteor/meteor/issues/9875#issuecomment-391471701
,
May 23 2018
Also, source files named in source maps (via `sources` and `sourcesContent`) previously show up automatically in the debugger's file tree, without having to be loaded into the workspace using the "Add folder to workspace" button. Now nothing appears in the workspace unless I add a folder manually. Besides the annoyance of having to add folders manually, this regression is unfortunate because there's not always a file on disk that corresponds to a file used by a source map, so adding folders manually is not an adequate workaround.
,
Jun 4 2018
Any Status? 67 shipped with the same bug. And This is not Windows only as originally submitted. This is also a problem on OSX. Thanks!
,
Jun 4 2018
,
Jun 4 2018
There's someone working on this bug, according to this github issue: https://github.com/ChromeDevTools/devtools-protocol/issues/103 Opened 11 days ago, replied to 8 days ago.
,
Jun 4 2018
Per mathieulj's comment, NiM https://chrome.google.com/webstore/detail/nodejs-v8-inspector-manag/gnhhdgbaldcilmgcpfddgdbkhjohddkj is a continued working solution.
,
Sep 10
Chrome version 69 has made the issue even worse according to this comment: https://github.com/ChromeDevTools/devtools-protocol/issues/103#issuecomment-420054427
,
Sep 11
,
Sep 25
,
Dec 16
Hi all this is now repaired with Chrome Version 71.0.3578.80 (Official Build) (64-bit) |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by caseq@chromium.org
, May 17 2018Components: -Platform>DevTools Platform>DevTools>JavaScript
Owner: eostroukhov@chromium.org
Status: Assigned (was: Unconfirmed)