From 5d498639908b75a8162802bdde073c796540350b Mon Sep 17 00:00:00 2001 From: zzstoatzz Date: Fri, 12 Jun 2026 16:24:27 -0500 Subject: [PATCH] build: bump mimalloc v2.3.2 -> v3.3.2 (canary RSS round two) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit the musl+mimalloc canary showed leak-shaped RSS growth that survived MIMALLOC_PURGE_DELAY=0, so it's live-allocation growth, not v2.x purge retention. mimalloc v2.x has a documented multithreaded peak-RSS pathology (microsoft/mimalloc#1111) reportedly fixed in v3.x — a strong match for ~2,800 thread-local heaps. v3.3.2 is the cheapest discriminator. source layout + override macros (MI_MALLOC_OVERRIDE / MI_LIBC_MUSL) are identical to v2; linkMimalloc unchanged. verified: static musl ELF builds, malloc override active, mi_collect/mi_version present. if v3 still leaks, next isolation is glibc+mimalloc (-Dtarget=...-gnu -Duse_mimalloc) to split allocator-cause from musl-libc-cause; prod glibc is flat, so the growth is allocator/libc, not zlay logic. Co-Authored-By: Claude Opus 4.8 --- build.zig.zon | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build.zig.zon b/build.zig.zon index 10e8974..c1bd773 100644 --- a/build.zig.zon +++ b/build.zig.zon @@ -21,8 +21,8 @@ .hash = "rocksdb-9.7.4-z_CUTsLJAAArLT8DEcD1Li7XthpIinhXrcitqQLFIKLK", }, .mimalloc = .{ - .url = "https://github.com/microsoft/mimalloc/archive/refs/tags/v2.3.2.tar.gz", - .hash = "N-V-__8AAFWPVAACRdwIuqz69BNLZ8fncUWjjv1FzFHiSsQW", + .url = "https://github.com/microsoft/mimalloc/archive/refs/tags/v3.3.2.tar.gz", + .hash = "N-V-__8AABIaVwAXht9TqAXbXVAua7yfLMIYLI6I6-ewET5p", }, }, .paths = .{ -- 2.51.2