hartator / gmail.com wrote: > Issue #11174 has been updated by hartator (Julien Khaleghy). > Any idea if it's already fixed somewhere else, or you guys > still working on it? I missed it, too :x (and now I'm too sleepy to continue...). It seems specific to glibc (tested 2.24-11+deb9 on Debian stable) and does not happen with jemalloc (3.6.0). And it is NOT because of memalign fragmentation, either(*); I disabled memalign usage to fallback to the aligned malloc+free fallback; but can still reproduce it. Finally, it needs multiple threads to reproduce the issue, a single thread is not enough. (*) https://sourceware.org/bugzilla/show_bug.cgi?id=14581 Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>