Stepping (Step Over / Step Out) after program completion causes the debugger to enter Node internal modules and sometimes crash, instead of safely terminating or ignoring the command.

[MatthewMonti]

Version

24.1.1 and 25.9.0 both issues where setting breakpoint and running steps crash debugger program on chrome, edge , or vscode.

Platform

Start debugger: node --inspect-brk app.js
Open Chrome DevTools: chrome://inspect
Step Into (F11) the addNumbers() function ✅ works
Step Out (Shift+F11) from function ✅ prints 15
Step Out again ❌ crashes into node:internal/process/promises:453

Subsystem

No response

What steps will reproduce the bug?

Node versions past version node 20.

How often does it reproduce? Is there a required condition?

This is produced when ever concluded step either step out or step over at last line of script fails to reset at end of script. In short js code completes then step over or step out crashes the debugger.

What is the expected behavior? Why is that the expected behavior?

Stepping (Step Over / Step Out) after program completion causes the debugger to enter Node internal modules and sometimes crash, instead of safely terminating or ignoring the command.

[github-actions]

This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.