Users of Ripgrep version 15.2.0, specifically the x86_64-unknown-linux-musl binaries, have reported occasional segmentation faults. These crashes manifest during searches of very large file trees conducted with a high degree of concurrency.
The segfault is linked to an integrity assertion failure within musl's mallocng, which is the memory allocator used by musl libc. The specific error occurs during a calloc call that originates from the opendir function, indicating a memory management issue when opening directories in large search operations.
The bug has been reproduced on OpenSUSE Tumbleweed Linux x86_64. Reproduction requires a sufficiently large search tree, approximately 20GiB across 1.8 million files, which can be generated using a provided Python script. Running Ripgrep in a continuous loop searching for a non-existent string on a 24-core system typically triggers the SIGSEGV within about a minute, especially when the search tree fits within the kernel's block cache.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
Ripgrep's x86_64-unknown-linux-musl binaries occasionally crash with a segmentation fault when performing very large searches with high concurrency. The issue occurs within musl's mallocng during a calloc operation made from opendir, indicating a memory integrity problem.