Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: clarify persistent ref behavior #42035

Closed
wants to merge 4 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 8 additions & 1 deletion doc/api/n-api.md
Expand Up @@ -1649,7 +1649,14 @@ the corresponding object on the heap being retained forever.

There can be multiple persistent references created which refer to the same
object, each of which will either keep the object live or not based on its
individual count.
individual count. Multiple persistent references to the same object
can result in unexpectedly keeping alive native memory. The native structures
for a persistent reference must be kept alive until finalizers for the
referenced object are executed. If a new persistent reference to the
is created for the same object, the finalizers for that object will not be
run and the native memory from the earlier persistent reference will
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
not be freed. This can be avoided by calling `napi_delete_reference`
in addition to `napi_reference_unref` when possible.
mhdawson marked this conversation as resolved.
Show resolved Hide resolved

#### `napi_create_reference`

Expand Down