Pin Node.js to 24.14.1 to avoid v24.15.0+ native crash - #67402
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Pins the Node.js version used by the Azure Pipelines “default-build” jobs to avoid intermittent native node.exe crashes seen on Windows CI after Node 24.18.0 started being picked up by the floating 24.x spec.
Changes:
- Change
UseNode@1fromversion: 24.xtoversion: 24.17.0in both job blocks indefault-build.yml. - Update the
Cache@2node_modulescache key/restoreKey segment fromnode24tonode24.17.0to avoid reusing caches produced with a different Node version.
Youssef1313
approved these changes
Jun 24, 2026
wtgodbe
enabled auto-merge (squash)
June 24, 2026 20:50
Node.js v24.15.0 and every later 24.x release (24.16.0, 24.17.0, 24.18.0) cause intermittent native crashes in node.exe on Windows CI agents. The current signature is a Windows access violation (0xC0000005, npm error code 3221225477 / MSBuild exit code -1073741819) inside node.exe while running 'rollup -c' for the Components JS workspaces. Crash frequency rises with each release; over the past week the rollup crash was observed on 24.16.0 (2x), 24.17.0 (3x) and 24.18.0 (4x) on the Build: Windows leg, while 24.14.1 had zero crashes. This matches the earlier v24.15.0 incident (0xDEAD during npm-ci extraction) that led to the original 24.14.1 pin (dotnet#66465), which was reverted in dotnet#66979. Re-pin to 24.14.1 (last release with zero observed crashes) until the upstream Node issue is fixed. Also update cache keys to avoid stale node_modules from 24.x builds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
wtgodbe
force-pushed
the
pin-node-24.17.0
branch
from
June 24, 2026 21:01
0089d8d to
3b859d5
Compare
wtgodbe
changed the title
mmitche
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Node.js v24.15.0 and every later 24.x release (24.16.0, 24.17.0, 24.18.0) cause intermittent native crashes in
node.exeon Windows CI agents. The current signature is a Windows access violation during the rollup bundling step of the Components JS build:Crash frequency per Node version (Build: Windows leg, past 7 days)
The crash spans the entire post-24.15.0 line — it is not unique to 24.18.0 (an earlier draft of this PR incorrectly pinned 24.17.0; data shows 24.17.0 also crashes). Frequency rises with each release. Example crashing builds: 1469128/1470089 (24.16.0), 1470543/1471858/1473856 (24.17.0), 1478676/1478854/1478907/1479647 (24.18.0).
Context — repeat offender
This matches the earlier v24.15.0 incident (0xDEAD during npm-ci extraction) that led to the original 24.14.1 pin (#66465 / #66621), reverted in #66979. With the pin gone,
24.xfloated up through 24.16/24.17/24.18 and hit the same class of upstream native crash. v24.14.1 ran Apr 24–Jun 8 with zero crashes.Fix
Re-pin to 24.14.1 (last release with zero observed crashes) in both
UseNode@1blocks ofdefault-build.yml, and bump cache keysnode24→node24.14.1. This is an upstream Node/V8 Windows regression, so a code-side fix isn't viable; pin until a fixed 24.x ships.