Frozen Realm doesn't reference count correctly#7504
Open
alecbarber wants to merge 1 commit intorealm:mainfrom
Open
Frozen Realm doesn't reference count correctly#7504alecbarber wants to merge 1 commit intorealm:mainfrom
alecbarber wants to merge 1 commit intorealm:mainfrom
Conversation
Contributor
|
@cla-bot check |
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: alecbarber.
|
|
The cla-bot has been summoned, and re-checked this pull request! |
ab0a5f0 to
84bbbcb
Compare
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.
Creating new instances of an already-cached version doesn't increment the reference count, which causes closing frozen Realm instances to be non-deterministic. The following code works as expected:
However, this code throws an
IllegalStateExceptionif the write operation doesn't happen between the two freeze operations:In a use-case where frozen RealmObjects/RealmResults are being temporarily created and there are concurrent write transactions (which is for example very easy to achieve with Kotlin Coroutines), cleaning up frozen Realms rapidly becomes non-deterministic.
This PR attempts to fix the issue by making the reference-counting behaviour of frozen Realms match that of live Realms – that is, every Realm instance created with
Realm.freeze()is active (and using resources) untilclose()is called on that instance.