microsoft / microsoft/mimalloc
Support for destroying heap from different thread
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
While destroying a heap from a thread that is different from the heap's creator, the `mi_segment_is_valid` assertion under `_mi_segment_page_free` fails. What would be required to add support for destroying heaps from arbitrary threads?
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 at the mi_segment_is_valid assertion under _mi_segment_page_free and trace the heap-destruction path for a heap created on another thread. Determine the allocator invariants that currently require the creator thread and define the checks or behavior needed for arbitrary-thread destruction; done means the failure is addressed and cross-thread destruction is covered by validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100