RoaringBitmap / RoaringBitmap/roaring
Fault When Creating Frozen Bitmap From MMapped
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
We have been trying to use Frozen Bitmaps for our internal system and were met with unanticipated faults. After working with @a392n328 we were able to write up this minimal failure, which is in #362. The actual error is
=== RUN TestFrozenCases
unexpected fault address 0x15fb008
fatal error: fault
[signal SIGBUS: bus error code=0x2 addr=0x15fb008 pc=0x11ed56a]
I can't figure out what exactly could be causing this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal failure described in issue #362 and reproduce the TestFrozenCases failure. Trace the frozen bitmap creation from the test until the SIGBUS occurs; done means identifying and fixing the fault and confirming that TestFrozenCases passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100