Fixed 64-bit alignment panic in chunkedContentCoder on 32-bit platforms. #148
+2
−1
Conversation
This file contains 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
Following the fix in blevesearch#147, a 'panic: unaligned 64-bit atomic operation' is still occurring on some platforms. As noted in blevesearch#147, this commit implements the alternative fix by placing the bytesWritten field at the top of the struct. Per the Golang sync/atomic documentation, on ARM, 386 and 32-bit MIPS systems, this is the reliable way to prevent these issues. Signed-off-by: Callum Jones <[email protected]>
abhinavdangeti
approved these changes
Feb 17, 2023
There was a problem hiding this comment.
Thanks for the contribution @cj123 . Looks good to me. Let's wait on one other review.
abhinavdangeti
requested review from
metonymic-smokey,
moshaad7 and
Thejas-bhat
Thejas-bhat
approved these changes
Feb 20, 2023
abhinavdangeti
pushed a commit
that referenced
this pull request
Feb 3, 2025
It's the same story as per #148, but for v16. ``` panic: unaligned 64-bit atomic operation goroutine 1 [running]: internal/runtime/atomic.panicUnaligned() /root/go/pkg/mod/golang.org/[email protected]/src/internal/runtime/atomic/unaligned.go:8 +0x2d internal/runtime/atomic.Xadd64(0xa0226e4, 0x0) /root/go/pkg/mod/golang.org/[email protected]/src/internal/runtime/atomic/atomic_386.s:125 +0x11 github.com/blevesearch/zapx/v16.(*invertedIndexOpaque).incrementBytesWritten(...) /root/go/pkg/mod/github.com/blevesearch/zapx/[email protected]/section_inverted_text_index.go:401 github.com/blevesearch/zapx/v16.(*invertedIndexOpaque).writeDicts(0xa022608, 0xfd7efa8) /root/go/pkg/mod/github.com/blevesearch/zapx/[email protected]/section_inverted_text_index.go:529 +0xe74 github.com/blevesearch/zapx/v16.(*invertedTextIndexSection).Persist(0x9424880, 0xfe720c0, 0xfd7efa8) /root/go/pkg/mod/github.com/blevesearch/zapx/[email protected]/section_inverted_text_index.go:54 +0x3d github.com/blevesearch/zapx/v16.(*interim).convert(0xfe5fc00) /root/go/pkg/mod/github.com/blevesearch/zapx/[email protected]/new.go:220 +0x6d9 github.com/blevesearch/zapx/v16.(*ZapPlugin).newWithChunkMode(0x9424880, {0xf774008, 0x3e9, 0x3e9}, 0x402) /root/go/pkg/mod/github.com/blevesearch/zapx/[email protected]/new.go:69 +0x194 github.com/blevesearch/zapx/v16.(*ZapPlugin).New(0x9424880, {0xf774008, 0x3e9, 0x3e9}) /root/go/pkg/mod/github.com/blevesearch/zapx/[email protected]/new.go:45 +0x43 github.com/blevesearch/bleve/v2/index/scorch.(*Scorch).Batch(0x9fde008, 0xf6ffa90) /root/go/pkg/mod/github.com/blevesearch/bleve/[email protected]/index/scorch/scorch.go:445 +0x63a github.com/blevesearch/bleve/v2.(*indexImpl).Batch(0x9c98500, 0xf6bf680) /root/go/pkg/mod/github.com/blevesearch/bleve/[email protected]/index_impl.go:316 +0x90 ```
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.
Following the fix in #147, a 'panic: unaligned 64-bit atomic operation' is still occurring on some platforms.
As noted in #147, this commit implements the alternative fix by placing the bytesWritten field at the top of the struct. Per the Golang sync/atomic documentation, on ARM, 386 and 32-bit MIPS systems, this is the reliable way to prevent these issues.