Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on Aug 27, 2026. It is now read-only.
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.
Maybe I'm missing something, but I wonder why we even create a new global ref to the same object if we then release the old handle? This means that we own the gref and we could maybe just keep using it without the need to create a new one? I must be missing something 🤔
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.
The peer's current
PeerReference(orig) might not be a global ref — it could beInvalidtype (fromSetPeerReferencewith a rawjobject), a local ref, or a weak global ref.NewGlobalRef()ensures we get a proper global ref regardless of the input type. We can't just keep using the existing ref because:Invalidtype, JNI operations on it may fail or behave unpredictablySo
NewGlobalRef+Dispose(old)normalizes any ref type into a proper global ref.