fix: add SharedArrayBuffer support and fix byteOffset handling across all buffer paths#370
Merged
Merged
Conversation
…ensure byteOffset works with all methods
edusperoni
changed the title
NathanWalker
approved these changes
May 11, 2026
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
2 participants
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.
The C++ interop path (TryGetBufferFromArrayBuffer) and several call sites
were not accounting for ArrayBufferView.byteOffset(), causing data
corruption when passing typed array views with non-zero offsets as void*
or incomplete array parameters. Additionally, SharedArrayBuffer was not
recognized anywhere in the runtime.
handles SharedArrayBuffer
instead of inline buffer access; NSData wrapping and debug validation
recognize SharedArrayBuffer