Skip to content

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. #62765

Closed as not planned
Closed as not planned
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.#62765
Labels
inspectorIssues and PRs related to the V8 inspector protocol.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@MatthewMonti
MatthewMonti
opened on Apr 16, 2026

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.

Activity

  1. MatthewMonti
    changed the title [-]Debugger Step Out / Step Out crashes into internal Promise files in Node 24.14.1 and 25.9.0[/-] [+]### Node JS Debugger not working in VSCode has a bug that causes debugger to crash. [/+] on Apr 16, 2026
  2. MatthewMonti
    changed the title [-]### Node JS Debugger not working in VSCode has a bug that causes debugger to crash. [/-] [+]Node JS Debugger not working in VSCode has a bug that causes debugger to crash. [/+] on Apr 16, 2026
  3. MatthewMonti
    changed the title [-]Node JS Debugger not working in VSCode has a bug that causes debugger to crash. [/-] [+]issues where setting breakpoint and running steps crash debugger program on chrome, edge , or vscode.[/+] on Apr 16, 2026
  4. MatthewMonti
    changed the title [-]issues where setting breakpoint and running steps crash debugger program on chrome, edge , or vscode.[/-] [+]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.[/+] on Apr 17, 2026
  5. joyeecheung
    added
    inspectorIssues and PRs related to the V8 inspector protocol.
    on Apr 19, 2026
  6. nodejs-github-bot
    added a commit that references this issue on Apr 23, 2026

    test: normalize known inspector crash as completion

    3dc06ae
  7. aduh95
    added 2 commits that reference this issue on May 5, 2026

    test: normalize known inspector crash as completion

    33c5f7f

    test: normalize known inspector crash as completion

    da4dd86

  8. github-actions commented on Jul 20, 2026

    @github-actions
    github-actionsbot
    on Jul 20, 2026 – with GitHub Actions
    Contributor

    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.

  9. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jul 20, 2026
  10. avivkeller
    closed this as not plannedon Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    inspectorIssues and PRs related to the V8 inspector protocol.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions