RipGrep Musl Binaries Crash: A Consensus Report
Executive TL;DR:
- RipGrep musl binaries occasionally crash during very large searches.
- The issue is related to the default allocator in musl.
- Replacing the default allocator with a more performant one can improve performance.
The Internet’s Verdict: 70% Hyped, 30% Skeptical
The Issue
RipGrep musl binaries have been reported to occasionally crash during very large searches. This issue has been attributed to the default allocator in musl, which can lead to contention during multithreading.
Forum Voices
According to one user,
I get why people don’t bother replacing the default allocator from musl all the time (it’s there, convenient). But in an application whose purpose is to be FAST, I find it weird they haven’t bothered replacing it with another more performant one.
Another user pointed out that
Switching to mimalloc improved performance by 20x, very close to what glibc offers by default, and just a bit under a glibc + mimalloc configuration.
Analysis
A detailed analysis of the issue can be found on GitHub, which provides insight into the kernel bug that may be contributing to the problem.
Conclusion
In conclusion, the issue with RipGrep musl binaries crashing during large searches is a complex one, and replacing the default allocator with a more performant one may be a viable solution.
Focus Keyword: RipGrep Crash