mimalloc-pprof

mimalloc with native pprof-compatible heap profiling — on Windows, Linux, and macOS alike.

The one mimalloc heap profiler that runs natively on Windows. Upstream mimalloc has no profiler at all, and the only other known implementation (Bun's) is POSIX-only — its stack capture is guarded behind glibc/Apple <execinfo.h>.

mimalloc as a Rust global allocator, with pprof-compatible sampled heap profiling built in. Windows is a first-class target alongside Linux and macOS.

Dumps open directly in google/pprof for flame graphs, call graphs, top reports, and profile diffs.

Usage

[dependencies]
mimalloc-pprof = "0.9"

[profile.release]
debug = "line-tables-only"
strip = false

Profiling hooks are enabled by default, preserving the behavior of earlier releases. If an application only needs mimalloc and wants to compile the profiler out, opt out of the default feature:

[dependencies]
mimalloc-pprof = { version = "0.9", default-features = false }

With default-features = false, the allocator remains available and the profiling API is retained for source compatibility, but profiling cannot be started (prof::start and enable_heap_profiling return false).

use mimalloc_pprof::{prof, MiMalloc};
use std::path::Path;

#[global_allocator]
static ALLOCATOR: MiMalloc = MiMalloc;

fn main() -> std::io::Result<()> {
    assert!(prof::start(0), "profiler already running"); // 0 = default, ~512 KiB

    let retained = vec![0_u8; 1024 * 1024];
    prof::dump_file(Path::new("heap.prof"))?;            // dump while still live
    std::hint::black_box(&retained);

    prof::stop();
    Ok(())
}

Then:

pprof -http=:0 ./target/release/my_app heap.prof

Or profile without touching the code at all:

MIMALLOC_PROF=1 MIMALLOC_PROF_DUMP_AT_EXIT=heap.prof ./my_app

Versions

The profiler API, environment variables, and output formats are identical in both, so moving between them is a version bump rather than a code change.

0.9.x is recommended. It has strictly more test coverage, per-heap allocator statistics, and fixes two upstream mimalloc bugs that 0.8.x still carries — including an unbounded memory leak on Windows/MinGW where every exiting thread leaked its heap and pages (23.5 GB at 100 stress iterations, versus flat after the fix). Note that upstream mimalloc v3 is itself still a pre-release branch.

Exact statistics alongside sampled ones

On 0.9.x, prof::stats() carries the allocator's exact counters next to the sampled ones. A sampled profile alone cannot tell you whether it under-counted; comparing the two measures the sampling error directly:

let s = mimalloc_pprof::prof::stats();
println!(
    "sampled live: {} bytes in {} samples; allocator committed: {}, requested: {}",
    s.live_bytes, s.live_samples, s.heap.committed, s.heap.malloc_requested,
);

Platforms and cross-compilation

The crate vendors mimalloc as a single amalgamated C translation unit with no autotools or CMake step, so it builds wherever cc-rs can reach a C compiler — including cross-compiled builds, in every direction.

Windows ARM64 needs one adjustment, and the crate makes it itself. In plain C mode mimalloc models C11 atomics with a deprecated MSVC Interlocked wrapper whose _acq/_rel ARM64 intrinsics clang-cl does not declare, so a cargo-xwin cross build of aarch64-pc-windows-msvc cannot compile it. Since 0.9.3 the build script selects clang's C11 stdatomic implementation for that target instead.

That choice is deliberately made in build.rs rather than left to the caller: CFLAGS is process-global for every cc-rs build script in a build, so a consumer trying to fix this from the outside — for example with CFLAGS=-TP to force mimalloc's C++ atomics path — also changes the language mode of every other native dependency in the graph. Nothing outside this crate should have to know how its atomics are selected.

Notes

• On Linux and macOS, keep frame pointers for reliable stack walking: rustflags = ["-Cforce-frame-pointers=yes"] in .cargo/config.toml. Windows x64 uses unwind information instead — keep the PDB.
• Do not link a second mimalloc into the same process; this crate vendors its own.

Full documentation, the C API, and the upstream-bug details are in the repository README.

License

MIT, the same as upstream mimalloc.