Skip to content

Fix --prof-startup never being able to profile renderer/extension host#307849

Open
winstliu wants to merge 1 commit intomicrosoft:mainfrom
winstliu:fix-debug-ports
Open

Fix --prof-startup never being able to profile renderer/extension host#307849
winstliu wants to merge 1 commit intomicrosoft:mainfrom
winstliu:fix-debug-ports

Conversation

@winstliu
Copy link
Copy Markdown
Member

@winstliu winstliu commented Apr 4, 2026

--remote-debugging-port is documented as only accepting a port.
Similarly, --inspect-brk-extensions runs through parseDebugParams, which directly tries to convert the argument into a number.

So, remove the host from both arguments.

Copilot AI review requested due to automatic review settings April 4, 2026 22:15
@vs-code-engineering
Copy link
Copy Markdown
Contributor

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@bpasero

Matched files:

  • src/vs/code/node/cli.ts

@deepak1556

Matched files:

  • src/vs/code/node/cli.ts

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes --prof-startup startup profiling by ensuring Electron/Node debug-related CLI switches are passed in the format they actually accept, so renderer and extension host profiling can attach successfully.

Changes:

  • Pass --remote-debugging-port as a port-only value (no host).
  • Pass --inspect-brk-extensions as a port-only value (no host), matching parseDebugParams behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants