By jemalloc 5.4.0 shipped this week — the first significant release in seven years. The memory allocator running inside Firefox, Redis, FreeBSD, and Meta’s server infrastructure is alive again, and the changes in this release are more substantial than a quiet GitHub tag suggests.
A Six-Year Silence, Then a Hard Reset
jemalloc 5.3.0 shipped in 2019. For the next six years, the project barely moved. In June 2025 the GitHub repository was quietly archived — no announcement, no migration path, no named successor. Jason Evans, the allocator’s original author, had already left Meta. The Hacker News thread that followed was part eulogy, part alarm: Redis bundles jemalloc by default. Firefox ships it. FreeBSD uses it as the default libc allocator. Half of open-source infrastructure runs on this thing, and it just blinked off.
Nine months later, Meta published a candid engineering post admitting they had accumulated technical debt, drifted from open-source principles, and were recommitting to jemalloc. The repository was unarchived. Dedicated engineers were assigned. Evans was consulted. Five months after that, 5.4.0 appeared on GitHub with 160+ commits.
What Actually Changed in 5.4
The headline work is infrastructure, not new features — which is appropriate for a codebase that needs to be reliable for another decade.
OS abstraction layer. Previously, platform-specific code was scattered through the codebase as #ifdef blocks. 5.4 extracts all of it — file I/O, time, synchronization, CPU topology, virtual memory, error handling — into a unified OS layer. The immediate wins are MinGW and macOS fixes. The longer-term win is that contributing platform support no longer requires touching the allocator’s internals.
Front-end modularization. The monolithic jemalloc.c has been split apart. Arena management, fork orchestration, and allocation dispatch now live in separate modules with no circular header dependencies. This matters for maintenance and for anyone building custom allocator tooling on top of jemalloc.
New allocation primitives. EXTENT_ALLOC_FLAG_PINNED lets you mark HugeTLB-backed extents as non-reclaimable in custom extent hooks — useful if you’re pre-allocating huge pages for latency-sensitive services. Per-CPU arena selection via thread.arena gives NUMA-aware applications a way to pin threads to the arena on their socket.
The Breaking Change You Need to Know
One change will bite upgraders: the old fixed tcache policy is gone. Seven mallctl controls — including opt.tcache_max and thread.tcache.enabled — have been removed and replaced with an adaptive per-bin policy.
If your application manually tuned tcache via mallctls (common in Redis-adjacent stacks and custom latency tuning setups), those calls will now fail. Before upgrading, grep your codebase for tcache in any mallctl calls and remove them. The adaptive policy outperforms the old fixed targets in most workloads — but the migration is manual.
Why the Fragmentation Argument Still Holds
jemalloc doesn’t make programs faster at the CPU level. What it does is keep resident set size (RSS) from bloating over time under bursty, multi-threaded allocation patterns — which glibc malloc handles poorly.
The numbers are real. A FastAPI service that had been pinned at its 1 GiB memory cap due to fragmentation under async load cut its RSS by 47% (873 MB to 458 MB) with a 14-line Dockerfile change swapping in jemalloc. LinkedIn’s Venice platform eliminated steady RSS growth across its server fleet after the same swap. Smaller RSS means less swap risk, lower cloud memory bills, and more headroom before OOM kills start.
How to Get It
The fastest path is LD_PRELOAD — no recompile needed:
LD_PRELOAD=/usr/local/lib/libjemalloc.so.2 ./myappFor Rust services, tikv-jemallocator provides the GlobalAlloc implementation:
#[global_allocator]
static GLOBAL: tikv_jemallocator::Jemalloc = tikv_jemallocator::Jemalloc;Build from source or grab the binaries from the 5.4.0 release page. Most Linux distros will have updated packages within a few weeks. Check the Phoronix coverage for distro-specific notes.
jemalloc being actively maintained again is worth more than any individual feature in this release. 5.4 is cleanup and foundations — that’s exactly what a project needs after six years of stagnation, and it signals that the next releases will be able to build on stable ground.
