Port GC checkpoint runtime work for #1090 - #1324
Merged
proggeramlug merged 2 commits intoMay 22, 2026
Merged
Conversation
4 tasks
proggeramlug
added a commit
that referenced
this pull request
May 22, 2026
…sweep (#1414) Rolls up 26 PRs that merged to main post-v0.5.1023 without version bumps: - node:crypto gap-fixes (#1386 #1393 #1394 #1402 #1405): randomInt, timingSafeEqual, getHashes/getCiphers, sha224/sha384, base64 digest, Buffer hash input, no-arg digest() → Buffer, pbkdf2Sync digest arg, scryptSync. - node:perf_hooks (#1321 + #1328 #1342 coverage): performance + User Timing + PerformanceObserver native impl, granular node-suite + edge-case coverage. - #1090 GC checkpoint runtime work (#1324). - #1311 geisterhand on iOS (#1316 #1383 #1384 #1385). - #1312 process.env.X (unset) is nullish undefined (#1314). - #1319 thread-safety hardening for cross-thread runtime statics. - #1322 exact-head GC evidence packet. - #1323 wasm timers dispatch through mem_call bridge (#1329). - #1317 node:timers/promises shadow-segfault fix (#1326). - #1330 node:process suite (#1331). - #1292 bcrypt.hash() returns String (#1307). - #1293 fastify .json()/.body external-fastify dispatch (#1308). - #1296 app pattern performance gaps. - #1297 diagnostics_channel parity. - #1301 iOS App Groups capability (#1313). - #1318 #1325 os/methods/modern-methods static dispatch. - #1315 expanded Node parity test coverage. - #1382 ui-ios stdlib pump for async fetch. - #1392 ui-wasm reactive state + setText (#1404).
2 tasks
proggeramlug
added a commit
that referenced
this pull request
May 22, 2026
…1422) PR #1324 ("Port GC checkpoint runtime work for #1090", e933b89) reverted the 290/315 MB ceiling from v0.5.1022 (#1286 / 4fcfddb) back to 250/275 while rewriting the surrounding comments. The v0.5.1024 release-packages compile-smoke job then hit the same Ubuntu overrun we already fixed once: default 268 MB / limit 250 MB (+7%) gen-gc-explicit 268 MB / limit 250 MB (+7%) force-evac+verify 288 MB / limit 275 MB (+5%) Restore the wider ceiling and replace the comment with one that references the actual rebump history (v0.5.1024 measurements + the #1324 revert) so the next contributor doesn't accidentally undo it again. Production binaries are stripped by the linker; these RSS figures are unstripped release-build artefacts used as a regression signal, not a deployment-size measurement. Refs #1090 #1286 #1324.
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.
Summary
This is the substantive runtime GC checkpoint toward #1090. It is intentionally separate from #1322, which only adds exact-head evidence tooling.
This PR ports the completed GC architecture work onto the split runtime tree and keeps the public GC facade/ABI intact while moving the collector toward the #1090 invariant:
What changed
crate::gc::*and exported C ABI entrypoints.Follow-up fix included in the port
While validating the port, I found and fixed a few real split/port gaps:
value/reasonstores now route through GC-aware slot storesVerification
Passed locally on branch
codex/gc-1090-checkpoint-port-20260522at072055c42741f394ab8092c0ef51a1bd7a11a126:cargo fmt --checktests/test_gc_store_site_inventory.sh-> 188 files scannedcargo check -p perry-runtimecargo check -p perry-codegencargo test -p perry-runtime --release runtime_roots -- --test-threads=1-> 54 passedcargo test -p perry-runtime --release gc::tests -- --test-threads=1-> 274 passedcargo test -p perry-codegen --test large_object_barriers-> 3 passedcargo test -p perry-codegen --test typed_shape_descriptors-> 12 passedcargo build --release -p perryscripts/run_memory_stability_tests.sh-> 60 PASS / 0 FAILgit diff --checkMemory stability highlights from the final run:
test_memory_json_churn.tsdefault: 236 MB / 250 MBtest_memory_json_churn.tsgen-gc-explicit: 236 MB / 250 MBtest_memory_json_churn.tsforce-evac+verify: 258 MB / 275 MBtop_remaining_reason=none07_object_create,12_binary_trees, andbench_gc_pressureScope
Refs #1090. This is a strong checkpoint toward #1090, not the final closing packet. The remaining closure work is full exact-head benchmark evidence, broader production policy hardening, and the rest of the long-term old-gen/typed-layout roadmap.