microsoft / microsoft/mimalloc
IOS crash --- "pointer being freed was not allocated"
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
malloc: *** error for object 0x106890000: pointer being freed was not allocated
(3874,0x103cfb880) malloc: *** set a breakpoint in malloc_error_break to debug
but it would be ok if I do not link the mimalloc
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 by reproducing the reported iOS crash from the issue's malloc error log, comparing a build linked with mimalloc against one without it. The report names no source files or tests, so locating the allocation and deallocation path is part of the investigation; done means the crash no longer occurs in the mimalloc-linked build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ios
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100