Repository navigation
fix: avoid null pointers in zero-length memory copies - #514
Merged
Merged
Conversation
SteNicholas
reviewed
Nov 5, 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
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.
Purpose
Empty string keys trigger UBSan reports when
MemorySlice::CopyBytes()passes null pointers tomemcpy, even when the copy length is zero.Skip zero-length copies in:
MemorySlice::CopyBytes()MemorySegment::GetOrCreateHeapMemory()ByteArrayInputStream::Read()overloadsTests
Added regression coverage:
MemorySliceTest.TestSliceCopyEmptyBytesMemorySegmentTest.TestGetOrCreateHeapMemoryForEmptySegmentByteArrayInputStreamTest.TestZeroLengthReadByteArrayInputStreamTest.TestZeroLengthReadFromEmptyStreamAPI and Format
Documentation
Generative AI tooling
Generated-by: OpenAI Codex (GPT-6)