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

Issue 839727 link

Starred by 2 users
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 8
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools failed to link network resource to filesystem.

Reported by lacm...@gmail.com, May 4 2018 
DevTools failed to link network resource to filesystem.

Platform: Win
Chrome version: 66.0.3359.139

What are the details of your project?
- HTTP server: node HTTP version 10.0.0 with --inspect parameter

In prior chrome version it works, but now, it doesn't map the same path with nodejs sources: 

file:///C:/x/y.js to file:///c:/x/y.js

I've made a proxy, that convert the debugger protocol paths... but it fails in this Chrome version.
mappingbug.jpg
74.0 KB View Download

Comment 1 by susan.boorgula@chromium.org, May 6 2018

Labels: Needs-Triage-M66

Comment 2 by sindhu.chelamcherla@chromium.org, May 7 2018

Labels: Triaged-ET
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning the issue to 	lushnikov@ - owner of similar bugs  805501 ,  801066 .

lushnikov@: Request you to please have a look into the issue and help in further triaging.

Thanks..

Comment 3 by lacm...@gmail.com, May 8 2018 

I found a new relation! If i start my process from a .bat file and not from a cmd.exe, it works fine!

Context influence the path???

Comment 4 by lacm...@gmail.com, May 8 2018 

...another one: if i use NiM, and it opens the devtools, mapping not working again

Comment 5 by lushnikov@chromium.org, Dec 8

Status: Archived (was: Assigned)
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story.
►

Sign in to add a comment