The debugger doesn't work properly in versions > 46

[irtaza-ebryx]

Issue Type: Bug

• Set a breakpoint
• Keep the file with the breakpoint open
• Start debugger on a NodeJS project
• The breakpoint dissappears.
• When the breakpoint is hit, the same file is opened with the debugger stopped at the breakpoint. And in this file the breakpoint is also visible.

P.S. In versions <= 47.2 debugging wasn't working at all. The behavior above is for versions >= 47.3.

VS Code version: Code 1.46.1 (cd9ea64, 2020-06-17T21:13:08.304Z)
OS version: Linux x64 4.15.0-112-generic

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Screen Reader	no
DESKTOP_SESSION	ubuntu
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

Extensions (13)

Extension	Author (truncated)	Version
bracket-pair-colorizer	Coe	1.0.61
gitlens	eam	10.2.2
gc-excelviewer	Gra	3.0.39
easy-icons	jam	0.3.1
dotenv	mik	1.0.1
graphql	mqu	0.1.2
vscode-docker	ms-	1.4.1
python	ms-	2020.7.96456
prisma	Pri	2.3.0
nunjucks	ron	0.3.0
code-settings-sync	Sha	3.4.3
octave	toa	0.0.3
pdf	tom	1.1.0

[connor4312]

Please collect a trace log using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

/needsMoreInfo

[altair-jan]

Guys, I see the same issue. This started happening after the latest update. Please fix it and really annoying and making unusable. I have to put debugger in the code to actually hit the breakpoint.

[altair-jan]

@connor4312 - I have emailed the log, please do the needful.

[connor4312]

In the log you sent, it doesn't look like you hit a breakpoint at all. Can you send a log where you do this?

The most common cause of this problem is using Node 8 (which is end of life as of 2020) and the best solution to the problem is to update to a most recent version if possible. A complete log file will determine whether this is happening for you.

[altair-jan]

That is the issue where when I set a breakpoint, it says its unbound and doesn’t hit. From: Connor Peet <notifications@github.com> Reply-To: microsoft/vscode <reply@reply.github.com> Date: Wednesday, August 19, 2020 at 10:52 AM To: microsoft/vscode <vscode@noreply.github.com> Cc: Lakshmi Janardhan <jan@altair.com>, Comment <comment@noreply.github.com> Subject: Re: [microsoft/vscode] The debugger doesn't work properly in versions > 46 (#104781) In the log you sent, it doesn't look like you hit a breakpoint at all. Can you send a log where you do this? The most common cause of this problem is using Node 8 (which is end of life as of 2020) and the best solution to the problem is to update to a most recent version if possible. A complete log file will determine whether this is happening for you. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fmicrosoft%2Fvscode%2Fissues%2F104781%23issuecomment-676475076&data=02%7C01%7Cjan%40altair.com%7Cee3cd1d3d7ec4bcc98ea08d8444f77b8%7C2bae5b570eb848fbba47990259da89d2%7C0%7C1%7C637334455391852212&sdata=TuNoHX7OvFuEpr6BgaGbpp4qg7Vwm8RUckBzZR%2F44ak%3D&reserved=0>, or unsubscribe<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.luolix.top%2Fnotifications%2Funsubscribe-auth%2FAOPFPLD42GUZA7BP4BHZMR3SBPRJ7ANCNFSM4QBJPVKA&data=02%7C01%7Cjan%40altair.com%7Cee3cd1d3d7ec4bcc98ea08d8444f77b8%7C2bae5b570eb848fbba47990259da89d2%7C0%7C1%7C637334455391862209&sdata=7%2BlRZhEIq%2FiqYUEhdpH514SzGwbbYTYaXas0nzOdBpI%3D&reserved=0>.

[connor4312]

Okay. What version of Node are you using, and how are you launching the program you're trying to attach to?

[irtaza-ebryx]

I was running node version 8, tried version 10 and 12 using runtimeVersion option in launch.json, and it worked for me. Thanks.