Claude Bot 66a84b353d fix(napi): tie external buffer finalizer to ArrayBuffer lifecycle ...

Previously, `napi_create_external_buffer` used a two-stage finalization
approach: it created the ArrayBuffer with an empty finalizer, then added
the real finalizer separately via `vm.heap.addFinalizer()`. This caused
a race condition where native code could free/reuse the underlying memory
while Bun still held a reference to the ArrayBuffer.

The fix passes the finalizer directly to `ArrayBuffer::createFromBytes`,
matching the approach already used by `napi_create_external_arraybuffer`.
This ties the cleanup correctly to the ArrayBuffer's lifecycle.

Fixes #26423

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-24 20:34:16 +00:00

..

napi-app

fix(napi): tie external buffer finalizer to ArrayBuffer lifecycle

2026-01-24 20:34:16 +00:00

node-napi-tests

chore: remove duplicate words in comment (#25347)

2025-12-05 11:19:47 -08:00

uv-stub-stuff

gitignore the sources text files (#22408)

2025-09-04 14:59:35 -07:00

napi-value-ffi.test.ts

chore: bump TinyCC to latest upstream (Jan 2026) (#26210)

2026-01-18 13:31:21 -08:00

napi.test.ts

fix(napi): tie external buffer finalizer to ArrayBuffer lifecycle

2026-01-24 20:34:16 +00:00

uv_stub.test.ts

gitignore the sources text files (#22408)

2025-09-04 14:59:35 -07:00

uv.test.ts

Fix formatters not running in CI + delete unnecessary files (#19433)

2025-05-08 23:22:16 -07:00