test: Add GC lifecycle test for identity-cached wrappers#7
Merged
Conversation
Verify that WeakRef-based identity cache does not prevent garbage collection. Creates an identity-mode object, crosses it 5 times (filling identity cache), drops all references, triggers GC + event loop ticks, and asserts the Swift object is deallocated and deinit fires exactly once.
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.
Overview
Add a test proving that the WeakRef-based identity cache does not prevent garbage collection of Swift heap objects.
The existing GC lifecycle test (
testJSWrapperIsDeallocatedAfterFinalization) only covers non-identity classes. This adds an equivalent for@JS(identityMode: true)classes where the identity cache holds aWeakRefto the wrapper.What it tests
Creates a
RetainLeakSubject(identity-mode class), crosses it to JS 5 times (filling the identity cache with aWeakRefentry), drops all Swift-side references, triggers GC + event loop ticks, and verifies:weakSubject == nil)deinitfires exactly onceThis covers the scenario where only TypeScript holds a reference to an identity-cached Swift object, then that reference becomes unreachable.
What changed
IdentityModeTests.swift— AddedtestIdentityCachedWrapperIsReclaimedByGCasync test. Added@JSFunction gc()import (same pattern asSwiftClassSupportTests).Generated/BridgeJS.swift+Generated/JavaScript/BridgeJS.json— Regenerated to includegcimport binding.