News for hackers. Stuff that matters.
Re:RipGrep musl binaries occasionally segfault during very-l... by entrope on Saturday August 01, 2026 @05:04PM (#49138467)
I think ripgrep does avoid allocations in that innermost loop. That's why this report says all the crashes are associated with opendir() and its memory allocation: the opendir() call is outside of ripgrep's innermost loop but still runs often enough to trigger the race condition.
Re:RipGrep musl binaries occasionally segfault during very-l... by mort96 on Saturday August 01, 2026 @05:18PM (#49138598)
And that's why musl's allocator's performance isn't a huge concern for ripgrep
Re:RipGrep musl binaries occasionally segfault during very-l... by Orphis on Saturday August 01, 2026 @05:45PM (#49138785)
That's to be properly measured. Assuming that the allocator will not cause issues there is to be proven.

The application I recently improved by changing the allocator had a similar profile (a C++ include scanner) and thread parallel I/O functions had terrible performance originally with mallocng. Adding threads almost had negative value because of the contention.