sf project deploy report hangs and terminates with core dump on Linux CI (v2.118.20) #3484
Description
Summary
While running a metadata validation using sf project deploy report inside a Bamboo pipeline, the Salesforce CLI process (node inside the sf client distribution) intermittently terminates with a core dump (signal 3 / quit).
This occurs during the Running Tests stage of a deployment, with no deterministic pattern: the same package sometimes deploys correctly, and sometimes the CLI crashes.
The org operation (sf project deploy report --wait 600) hangs indefinitely and Bamboo forcibly terminates the job. Other deployments and other packages of similar size run without issues.
The problem started after updating to @salesforce/cli 2.118.20.
Steps To Reproduce
Unfortunately I cannot provide a public repo because the CI pipeline and metadata are internal to my company, but I can describe the exact scenario:
- Prepare a folder with standard Apex classes, tests, LWC and Custom Metadata (28 files total — nothing large or unusual).
- Trigger a validation using:
sf project deploy validate --target-org PROD_RM --manifest package.xml --test-level RunLocalTests
- Wait until the
Running Tests…phase. - Randomly (not every run), the CLI process freezes and Bamboo force-kills the entire process tree.
- The CLI exits with:
/sf/client/2.118.20/bin/node: Quit (core dumped)
Note: When it works, the validation completes normally. The failure is intermittent but frequent.
Expected result
The command sf project deploy report --wait 600 should poll the job status until completion, or time out gracefully.
The CLI should not crash or generate a core dump.
Actual result
During the Running Tests phase:
- the CLI stops producing output for several minutes
- Bamboo force-stops the job due to inactivity
- stack trace collection reveals:
/sf/client/2.118.20/bin/node: Quit (core dumped) - the Python wrapper raises:
Exception: Fail show operation status from Org: 'PROD_RM'
The crash originates from the Node binary shipped with the CLI distribution, not from the pipeline code.
Additional information
Excerpt from Bamboo logs
Found related process: pid: 3007 ... cmd: sf/client/2.118.20/bin/node
Executing kill -3 3007
/sf/client/2.118.20/bin/node: line 45: 3007 Quit (core dumped)
The package deployed is small and contains regular metadata types (Apex classes, tests, LWC, labels, CMDT definitions).
Other packages (larger or smaller) deploy without any issues.
I am available to provide additional logs (full CLI debug output, Bamboo logs, org job logs).
System Information
Shell / environment
Running inside Atlassian Bamboo Agent (Linux)
CLI version
{
"architecture": "darwin-arm64",
"cliVersion": "@salesforce/cli/2.118.20",
"nodeVersion": "node-v24.12.0",
"osVersion": "Darwin 25.2.0",
"rootPath": "/opt/homebrew/lib/node_modules/@salesforce/cli",
"shell": "zsh",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.39 (core)",
"@oclif/plugin-commands 4.1.37 (core)",
"@oclif/plugin-help 6.2.35 (core)",
"@oclif/plugin-not-found 3.2.72 (core)",
"@oclif/plugin-plugins 5.4.53 (core)",
"@oclif/plugin-search 1.2.36 (core)",
"@oclif/plugin-update 4.7.14 (core)",
"@oclif/plugin-version 2.2.36 (core)",
"@oclif/plugin-warn-if-update-available 3.1.52 (core)",
"@oclif/plugin-which 3.2.42 (core)",
"@salesforce/cli 2.113.6 (core)",
"agent 1.24.27 (core)",
"apex 3.8.7 (core)",
"api 1.3.3 (core)",
"auth 3.9.19 (core)",
"data 4.0.62 (core)",
"deploy-retrieve 3.23.16 (core)",
"info 3.4.96 (core)",
"limits 3.3.71 (core)",
"marketplace 1.3.8 (core)",
"org 5.9.45 (core)",
"packaging 2.23.3 (core)",
"schema 3.3.88 (core)",
"settings 2.4.51 (core)",
"sobject 1.4.79 (core)",
"telemetry 3.6.66 (core)",
"templates 56.3.71 (core)",
"trust 3.7.113 (core)",
"user 3.6.41 (core)",
"apex-code-coverage-transformer 2.14.1 (user) published 79 days ago (Mon Oct 27 2025) (latest is 2.15.2)",
"sfdx-plugin-source-read 1.5.6 (user) published 123 days ago (Sun Sep 14 2025)"
]
}