stepping over breakpoint appears to resume execution fully, vs stepping.

[cdaringe]

• VSCode Version: 1.5.3
• OS Version: osx 10.11.6

may be related to ##13096

here, i visually demonstrate (you may want to click to view the GIF in a larger window):

thanks!

[cdaringe]

it's also strange that when execution ends, the debugging bar/context remains. i would expect the debugging bar to disappear when execution finishes.

[alecl]

I've been running into this fairly often for months and it's highly frustrating. Anything that can be done to gather more info so it can be addressed?

[weinand]

What node.js version are you using?

Some version of node have a bug: see #5822
(which is due to his node bug: nodejs/node#7219)

[weinand]

@cdaringe execution of node.js does not stop because of this node bug: nodejs/node#1788

[alecl]

Had the same issue in 4.5 and 6.10.1.

[alecl]

Bugs in nodejs from 2 years ago. This is madness. Any suggested workaround or version that still works?

[weinand]

nodejs/node#7219 should be fixed in recent versions of node.js.

Does it help if you use the 'inspector' protocol (by addig a "protocol": "inspector" to your launch configuration?

[weinand]

I've just verified that nodejs/node#7219 was fixed for node.js >= 6.5.0

[weinand]

@alecl What VS Code version are you using?

[alecl]

Interesting. I updated to 6.10.2 and then found it still happening. I set "smartStep" to false and that seemed to fix it. smartStep is skipping lines of my code that are calling outside code even though I'm NOT stepping into the outside code.

VSCode 1.11.1

[weinand]

If you still see the problem in 6.10.2 then it is unrelated to nodejs/node#7219.
Do you have any watch expressions defined? Does the problem disappear if you remove the watches?

[alecl]

It still occurs if I remove the watches but I believe the issue is with the smartStep feature being enabled rather than that nodejs termination bug now that I'm on 6.10.2. I'll find/open a new issue for that. Thanks for your help.

[weinand]

@cdaringe could you please verify that your problem no longer occurs in VS Code 1.11.x and node.js >= 6.5.0 - thanks!

[cdaringe]

confirmed--it's working great! thx!