Extension Host crashes with VS Code 1.129.0 and Salesforce Extension Pack 67.5.0

[skostojohn]

Summary

After upgrading VS Code from 1.128.x to 1.129.0, the VS Code Extension Host repeatedly terminates unexpectedly when the Salesforce Extension Pack is enabled.

The issue does not occur when Salesforce extensions are disabled, and it is resolved by downgrading VS Code back to 1.128.1.

Environment

• OS: Pop!_OS 24.04 (Linux x64)

• Kernel: 7.0.11-76070011-generic

• VS Code:

  • Failing: 1.129.0
  • Working: 1.128.1

• Salesforce Extension Pack: 67.5.0

Relevant Salesforce extension versions:

salesforce.salesforcedx-vscode@67.5.0
salesforce.salesforcedx-vscode-core@67.5.0
salesforce.salesforcedx-vscode-services@67.5.0
salesforce.salesforcedx-vscode-apex@67.5.0
salesforce.salesforcedx-vscode-lightning@67.5.0
salesforce.salesforcedx-vscode-lwc@67.5.0
salesforce.salesforcedx-vscode-metadata@67.5.0

Steps to reproduce

1. Upgrade VS Code from 1.128.x to 1.129.0.
2. Open a Salesforce DX project.
3. Allow Salesforce extensions to activate.
4. The Extension Host terminates unexpectedly:

Extension host terminated unexpectedly 3 times within the last 5 minutes.

Relevant error from Extension Host log

PendingMigrationError: navigator is now a global in nodejs,
please see https://aka.ms/vscode-extensions/navigator

Stack trace points into:

salesforce.salesforcedx-vscode-core-67.5.0/dist/src/index.js

Utility.getConnectionType()

Omt.sendTelemetryEvent()

Troubleshooting performed

The following tests were performed:

• Confirmed issue occurs with Salesforce extensions enabled.

• Disabled Salesforce Extension Pack:

  • Result: Extension Host remains stable.

• Cleared Salesforce/VS Code workspace state:

  • Result: Issue persists.

• Started VS Code with code --log trace:

  • Issue was not reproduced in that session, but normal startup continued to fail.

• Tried VS Code setting:

"extensions.supportNodeGlobalNavigator": false

• Result: No change.

• Downgraded VS Code to 1.128.1:

  • Result: Issue resolved while keeping Salesforce Extension Pack 67.5.0 installed.

Expected behavior

Salesforce extensions should activate normally under VS Code 1.129.0 without terminating the Extension Host.

Actual behavior

The Extension Host crashes repeatedly after Salesforce extensions activate.

Additional notes

This appears to be a compatibility issue between VS Code 1.129.0's extension host runtime changes and Salesforce Extension Pack 67.5.0, possibly related to the Node.js navigator global migration.

A minimal workaround is to remain on VS Code 1.128.1 until compatibility is restored.

[svc-idee-bot]

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.

[mshanemc]

Utility.getConnectionType()
Omt.sendTelemetryEvent()

We don't have anything like this in this repo's code, but I traced those back to an internal telemetry services that posts events back through the org, where the navigator stuff is referenced. BUT the navigator change has been in for a long time.

Started VS Code with code --log trace:

Issue was not reproduced in that session, but normal startup continued to fail.

THAT is very odd.

Can you try disabling the telemetry? I'm not sure it'll help because these might get called before that check happens.

[skostojohn]

Thanks @mshanemc . Turned off telemetry for the Salesforce extensions and upgraded to VS Code 129 again - seems stable. Thanks for your assistance.

[konkonrong-lgtm]

I can reproduce the same PendingMigrationError on a newer setup as well:

Windows 11 x64
VS Code 1.132.0
Salesforce Extension Pack 67.7.1

With Salesforce telemetry enabled, Developer: Reload Window produced multiple:

PendingMigrationError: navigator is now a global in nodejs

during extension deactivation. The stack traces point to Utility.getConnectionType() in both salesforcedx-vscode-core-67.7.1 and salesforcedx-vscode-services-67.7.1.

I then disabled salesforcedx-vscode-core.telemetry.enabled and tried Reload Window again. The PendingMigrationError did not appear this time.

I’m not seeing the Extension Host crash from the original report though. In my case the old Extension Host exits with code 0.