fix(napi): Read reference ownership before calling finalizer to avoid crash #24203
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.
Fixes #23493.
What was happening here was that napi-rs was freeing the napi reference (here) during its finalize callback (which we call here). We then were reading the
ownership
field of that freed reference.For some reason on arm macs the freed memory gets zeroed, so the value of
ownership
was0
when we read it (i.e. it wasReferenceOwnership::Runtime
). We then freed it again (since we thought we owned it), causing the segfault.