Repository navigation
Retain cross-realm MessagePorts through forced GC - #856
Merged
Merged
Conversation
This was referenced Sep 20, 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
Active-listener retention covered same-realm and dedicated Worker MessagePorts, but explicit low-memory collection did not reach ServiceWorker isolates. Iframe transfers also treated a peer in another V8 context as a locally traceable peer, allowing the receiving wrapper to be reclaimed even though it had an active listener.
Change
onmessageandaddEventListenerValidation
WEBSCENE_HYBRID_V8_RUNTIME_TEST_FILTER=messageport-iframe-gc webscene_hybrid_v8_runtime_testsWEBSCENE_NATIVE_ENGINE_TEST_FILTER=service-worker-messageport-gc webscene_native_engine_testsgit diff --checkCloses #825