An open ripgrep issue reports the official musl binaries segfaulting inside musl's mallocng during very large concurrent searches

Sources: ripgrep issue 3494, discussion
Summary: Issue 3494, opened 2026-07-26 by dfoxfranke and still open, reports ripgrep 15.2.0 built for x86_64-unknown-linux-musl crashing with SIGSEGV on an integrity assertion in musl's mallocng, reached through a calloc call from opendir during directory traversal. The reporter states the affected binary is byte-for-byte identical to the one in the official 15.2.0 musl release archive and to the rg bundled with OpenAI Codex, and that the crash reproduces independently of Codex. A reproduction recipe is published: a generated tree of roughly 20 GiB across 1.8 million files, then rg in a loop for a literal absent from the tree, which the reporter says faults within about a minute on a 24-core machine with the tree in page cache. A core dump and the matching binary are attached. No maintainer diagnosis is visible on the issue, so whether the fault lies in ripgrep, in the ignore crate's walker, or in musl is unresolved.
Why it matters: The musl builds are the ones shipped for static distribution and bundled into other tools, so a crash reachable through ordinary traversal on a large tree affects users who never chose that build target.
Follow-up: Track whether a maintainer localizes the fault to ripgrep, the ignore crate, or musl.