Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unhandled error in debug adapter - Unhandled promise rejection: TypeError: Cannot read property 'line' of null #42162

Closed
Deilan opened this issue Jan 25, 2018 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@Deilan
Copy link

Deilan commented Jan 25, 2018

  • VSCode Version: Code 1.19.3 (7c4205b, 2018-01-25T10:36:34.867Z)
  • OS Version: Windows_NT x64 10.0.15063
  • Extensions:
Extension Author (truncated) Version
debugger-for-chrome msj 4.0.0

Debug Console's output:

******** Unhandled error in debug adapter - Unhandled promise rejection: TypeError: Cannot read property 'line' of null
    at ChromeDebugAdapter.<anonymous> (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:575:61)
    at Generator.next (<anonymous>)
    at C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:10:71
    at Promise (<anonymous>)
    at __awaiter (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:6:12)
    at details.forEach (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:566:48)
    at Array.forEach (native)
    at ChromeDebugAdapter.<anonymous> (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:566:25)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:7:58)

Steps to Reproduce:

  1. Angular CLI 1.6.5 project
  2. npm start
  3. Launch debugger
@isidorn isidorn assigned roblourens and unassigned isidorn Jan 26, 2018
@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Jan 26, 2018
@roblourens
Copy link
Member

This implies that sourcemaps are messed up in a strange way. Can you share the project with me? Or should I see it with a clean angular CLI project?

@roblourens roblourens added *duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster and removed *duplicate Issue identified as a duplicate of another issue(s) labels Jan 26, 2018
@Deilan
Copy link
Author

Deilan commented Jan 27, 2018

@roblourens here you are: https://github.com/deilan-issues-samples/vscode-issue-42162

  1. npm install
  2. npm start

I am able to reproduce it on 2 different Windows 10 x64 computers.

@roblourens
Copy link
Member

Thanks for the sample project. It's caused by a script in the sourcemap with a weird name - ["/Users/roblou/Documents/vscode-issue-42162/node_modules/moment/locale ^\\.\\/.*$"]. Looking at your build, I have no idea where the pattern at the end comes from. But it exposes a slight problem with how source paths are handled.

@roblourens roblourens added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Jan 28, 2018
@roblourens
Copy link
Member

roblourens commented Mar 9, 2018

Fixed last month by microsoft/vscode-chrome-debug-core@c8b3814

@roblourens roblourens added this to the March 2018 milestone Mar 9, 2018
@RMacfarlane RMacfarlane added the verified Verification succeeded label Mar 30, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants