Fix CICD release build failures caused by memory management bug #209
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.
Summary
Fixes intermittent CICD release build failures that were causing panics during garbage collection with the error "index out of bounds: the len is 2 but the index is 2".
Root Cause
Objects allocated with
alloc_bytes()were storing the padded allocation size (including 16-byte alignment) in their headers, but the garbage collector was using this inflated size for marking memory regions. This caused attempts to mark memory beyond block boundaries during GC, leading to index out of bounds errors in the bitmaps crate.Example failure case:
Technical Details
The bug was in
heap.rsline 1720:The
alloc_sizeincludes padding fromalloc_size_of()which adds 16-byte alignment, butsize_bytesis the actual requested object size.Why Only in Release Builds?
mark()would catch bounds violations in debug buildsChanges Made
mark_region()test_alloc_bytes_header_size_correctness()Test Plan
🤖 Generated with Claude Code