You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e1460c9
Browse filesBrowse the repository at this point in the historyBrowse files
[vcpkg-tool-nodejs] Update to 24.22.1 [qtwebengine] Remove concurrency blocks
https://nodejs.org/en/blog/release/v24.22.1
We hope this fixes the intermittent qtwebengine crash. According to GPT 6.1 Sol + @ras0219-msft :
> The strongest related upstream case is nodejs/node#65756: intermittent Windows x64 Node 24.19.0 child-process crashes with `0xC0000005`, with the affected test file varying between runs. It is a useful analogue, not the same workload.
>
> nodejs/node#65778 fixes a use-after-free in Node’s CppGC/Realm teardown. A wrapper can be collected before its Environment is freed but destroyed afterwards, leaving its destructor writing through a freed Realm. The documented trigger combines a Worker, `vm.Script`, memory-pressure GC, and worker exit.
>
> The v24 backport, nodejs/node#66168, reports reproducing the crash on 24.20.0 and passing its Windows stress reproduction with the fix.
>
> The backport landed October 7, 2026, as:
>
> `83b3431c25be9fdb739c1531313c4c12a227c00a`
>
> Node 24.21.0 was released September 8 and lacks that fix. Node 24.22.0, released October 14, includes it. 24.22.1, released October 21, is the current v24 release verified on October 22. Comparing tagged `src/cppgc_helpers-inl.h` independently confirms the old destructor and its replacement.
This also means the reduced concurrency part of microsoft#53435 clearly did not work, so that is reverted here.
0 commit comments