Startup segfault with mimalloc allocator overrides on Linux
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 168
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
On Arch Linux x86_64 with GCC 16.2.1 and glibc 2.44 (debug64 and release64 presets), self-built binaries crash immediately. Even wibo --help segfaults before main. The official release binaries are not affected.
codex determined this reason: libstdc++ initialization calls free(NULL), which resolves to mimalloc before its page map is initialized.
I will submit a short fix PR.
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 crash with the debug64 and release64 presets using the self-built binary and wibo --help. Inspect the mimalloc allocator override and its page-map initialization around the reported free(NULL) during libstdc++ startup. Done means self-built binaries reach main and wibo --help no longer segfaults on the stated Linux environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100