-
-
Notifications
You must be signed in to change notification settings - Fork 159
fix(runtime): preserve structured clone graph identity #8250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
proggeramlug
merged 3 commits into
PerryTS:main
from
proggeramlug:fix/8232-structured-clone
Aug 17, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| **`structuredClone` preserves graph identity.** | ||
|
|
||
| The recursion-only cycle guard is replaced by a GC-visible source-to-clone memo, so | ||
| cycles and repeated references keep their identity across objects, arrays, maps, | ||
| sets, regexps and buffers — a value reached twice now clones once and both edges | ||
| point at the same clone, as the structured-clone algorithm requires. Clone failures | ||
| raise `DataCloneError` as a `DOMException`, which let the `perf_hooks` `TypeError` | ||
| workaround go, and traversal roots are cleared on both the success and failure paths | ||
| so a completed clone does not retain the graph it walked. | ||
|
|
||
| The memo's entries are visited as mutable roots (`scan_structured_clone_memo_roots_mut`) | ||
| and its address-keyed lookup is rebuilt after visitation, because a copying collection | ||
| relocates either side. Registering that scanner is what the map clone test now does | ||
| explicitly: the GC test harness clears `MUTABLE_ROOT_SCANNERS` so a collection sees | ||
| exactly the roots a test installs, so without it the memo is decorative under test and | ||
| a clone's address is never rewritten across a forced copying minor. | ||
|
|
||
| Closes #8232. | ||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift
Do not claim immediate failure cleanup until the throw path clears the memo.
In
crates/perry-runtime/src/builtins/globals.rs:692-735, both clone entrypoints callclear_structured_clone_memo()only afterjs_structured_clone_innerreturns. The same code states that runtime throws uselongjmp, so aDataCloneErrorskips that call.reset_structured_clone_state()runs only before a later clone. A failed clone can therefore retain the graph in the thread-local memo. Clear the memo at the failure boundary, or change this entry to describe the deferred reset.🤖 Prompt for AI Agents