Many node processes are created from VS Code and do not go away

[peterTrifecta]

Summary

Ever since I upgraded to the latest CLI version salesforce/cli/2.123.1 darwin-arm64 node-v22.22.0 something is going on where the CLI has many node processes created when I have VS Code open. They end up taking up all of my computers memory and I have to shut down VS Code and kill them with ps -ef | grep node | grep -v grep | awk '{print $2}' | xargs sudo kill -9. Shutting down VS Code does not terminate the processes.

Steps To Reproduce

This is on a mac (see system information section below)

Be on the latest version @salesforce/cli/2.123.1 darwin-arm64 node-v22.22.0.
Open VS Code.
Open Activity Monitor.
Watch as the number of node processes grow. It takes some time, so perhaps it is periodical.

Expected result

Not to have an unreasonable amount of node processes generated until the computer's memory was exhausted.

Actual result

An unreasonable number of node processes were generated until the computer's memory was exhausted.

Additional information

The process is: /Users/peter.knolle/.local/share/sf/client/2.123.1-d33a2e4/bin/node

System Information

Using zsh, but this seems to be happening from VS Code.
sf version --verbose --json output:

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.123.1",
  "nodeVersion": "node-v22.22.0",
  "osVersion": "Darwin 25.2.0",
  "rootPath": "/Users/peter.knolle/.local/share/sf/client/2.123.1-d33a2e4",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.40 (core)",
    "@oclif/plugin-commands 4.1.40 (core)",
    "@oclif/plugin-help 6.2.37 (core)",
    "@oclif/plugin-not-found 3.2.74 (core)",
    "@oclif/plugin-plugins 5.4.56 (core)",
    "@oclif/plugin-search 1.2.38 (core)",
    "@oclif/plugin-update 4.7.19 (core)",
    "@oclif/plugin-version 2.2.36 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.55 (core)",
    "@oclif/plugin-which 3.2.43 (core)",
    "@salesforce/cli 2.123.1 (core)",
    "agent 1.30.4 (user) published 1 days ago (Sat Feb 21 2026)",
    "apex 3.9.6 (core)",
    "api 1.3.9 (core)",
    "auth 4.1.5 (core)",
    "code-analyzer 5.9.0 (user) published 26 days ago (Wed Jan 28 2026) (latest is 5.10.0)",
    "community 3.3.48 (user) published 79 days ago (Sat Dec 06 2025)",
    "data 4.0.68 (core)",
    "deploy-retrieve 3.24.8 (core)",
    "info 3.4.101 (core)",
    "limits 3.3.75 (core)",
    "marketplace 1.3.10 (core)",
    "org 5.9.66 (core)",
    "packaging 2.25.5 (user) published 2 days ago (Sat Feb 21 2026)",
    "schema 3.3.91 (core)",
    "settings 2.4.55 (core)",
    "sobject 1.4.82 (core)",
    "telemetry 3.7.2 (core)",
    "templates 56.4.7 (core)",
    "trust 3.7.113 (core)",
    "user 3.6.49 (core)",
    "@salesforce/sfdx-scanner 4.12.0 (user) published 299 days ago (Tue Apr 29 2025)",
    "sfdmu 5.6.0 (user) published 1 days ago (Sat Feb 21 2026)",
    "sfdx-git-delta 6.31.0 (user) published 10 days ago (Thu Feb 12 2026)",
    "sfdx-hardis 6.26.2-beta202602180959.0 (user) published 5 days ago (Wed Feb 18 2026) (latest is 6.26.2)",
    "texei-sfdx-plugin 2.8.5 (user) published 66 days ago (Thu Dec 18 2025)"
  ]
}

Doctor Output

=== Running all diagnostics

pass - salesforcedx plugin isn’t installed
pass - you don't have any linked plugins
pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
pass - using latest or latest-rc CLI version
pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
pass - [@salesforce/plugin-deploy-retrieve] default target DevHub max apiVersion matches default target org max apiVersion
warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches default target org max apiVersion
pass - can access: https://test.salesforce.com
pass - can access: https://appexchange.salesforce.com/services/data
pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
fail - [@salesforce/plugin-auth] CLI supports v2 crypto

Wrote doctor diagnosis to: /Users/peter.knolle/work/dev/b2b-commerce-rca/1771854531083-diagnosis.json

=== Suggestions

• Check https://github.com/forcedotcom/cli/issues for CLI issues posted by the community.
• Check http://status.salesforce.com for general Salesforce availability and performance.
• using npm registry https://registry.npmjs.org/ from npm config
• The sourceApiVersion in sfdx-project.json doesn't match the max apiVersion of the default target org. As a result, you're not using the latest features available in API version 66.0. The version mismatch isn't a problem, as long as it's the behavior you actually want.
• Your current installation of Salesforce CLI, including all the plugins you've linked and installed, doesn't yet support v2 crypto. All plugins and libraries must use at least version 6.7.0 of @salesforce/core to support v2 crypto. You're generally still able to successfully authenticate with your current CLI installation, but not if you generate a v2 crypto key.

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[cristiand391]

@peterTrifecta I'm unable to repro this, some questions:

1. are you opening vscode in a salesforce project?
2. are you using the salesforce vscode extensions? if so, please share the installed version
3. can try reloading the vscode instance with extensions disabled? see the screenshot below. This would help narrow down the origin.

[shetzel]

In the activity monitor when you click one of the node processes can you select the "Open Files and Ports" tab and report the contents. I suspect this might have been a recent change to telemetry and those processes are not exiting properly. If the contents of that tab mention uploader.js that's likely the problem.

[peterTrifecta]

I restarted with extensions disabled and the issue persisted. Here is the output of the "Open Files and Ports" tab:

/Users/peter.knolle/work/dev/b2b-commerce-rca
/Users/peter.knolle/.local/share/sf/client/2.123.1-d33a2e4/bin/node
/Library/Preferences/Logging/.plist-cache.VzVlXgNw
/usr/lib/dyld
/dev/null
/dev/null
/dev/null
count=0, state=0x8
->0x8ce0ee95f28c8148
->0x7c8b987bb5fb9b54
/
count=0, state=0xa
/
count=0, state=0xa
/
/private/var/folders/bf/2vkcy63n2xg_85vn9phvw8_r0000gn/T/sf-telemetry/telemetry-42da760fc893964ae0056581fa0ae7f96d39e695.log
->0x21903232214b3ad7
->0x6d84a8ed92bd4b73
count=0, state=0xa
/
/dev/null
/Users/peter.knolle/.sf/sf-2026-02-24.log
[ctl com.apple.netsrc id 7 unit 28]
->0xca12a520f370d674
192.168.1.6:64503->52.188.247.144:https

I'm executing a shell script, from the terminal within VS Code, that creates a scratch org, user, assigns many permission set licenses, a permission set group, and deploys, along with some queries and other manipulation.

[Damecek]

similar on my local machine, few hours after laptop restart this havoc. I do not use vs code, this comes directly from sf cli.

 - 202x Salesforce CLI telemetry upload
    .../@salesforce/plugin-telemetry/processes/upload.js

[Damecek]

looks fixed after update to @salesforce/cli/2.124.7