René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"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.","articleBody":"### Version\n\n24.1.1 and 25.9.0 both issues where setting breakpoint and running steps crash debugger program on chrome, edge , or vscode.\n\n### Platform\n\n```text\nStart debugger: node --inspect-brk app.js\nOpen Chrome DevTools: chrome://inspect\nStep Into (F11) the addNumbers() function ✅ works\nStep Out (Shift+F11) from function ✅ prints 15\nStep Out again ❌ crashes into node:internal/process/promises:453\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\nNode versions past version node 20. \n### How often does it reproduce? Is there a required condition?\nThis 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. \n\n### What is the expected behavior? Why is that the expected behavior?\nStepping (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.","author":{"url":"https://github.com/MatthewMonti","@type":"Person","name":"MatthewMonti"},"datePublished":"2026-04-16T00:41:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/62765/node/issues/62765"}