94 releases (13 breaking)

0.15.1 Apr 11, 2024
0.15.0-alpha.5 Mar 29, 2024
0.12.0-alpha.2 Dec 26, 2023
0.11.0 Nov 28, 2023
0.4.0 Mar 28, 2023

#163 in Memory management

Download history 876/week @ 2024-01-03 458/week @ 2024-01-10 667/week @ 2024-01-17 864/week @ 2024-01-24 943/week @ 2024-01-31 1037/week @ 2024-02-07 3025/week @ 2024-02-14 4033/week @ 2024-02-21 5666/week @ 2024-02-28 4719/week @ 2024-03-06 4667/week @ 2024-03-13 3007/week @ 2024-03-20 2677/week @ 2024-03-27 4087/week @ 2024-04-03 5841/week @ 2024-04-10 4329/week @ 2024-04-17

17,480 downloads per month
Used in 27 crates (5 directly)



Run-time memory tracking and profiling.

Part of the rerun family of crates.

Latest version Documentation MIT Apache

This is a library for tracking memory use in a running application. This is useful for tracking leaks, and for figuring out what is using up memory.

re_memory includes an opt-in sampling profiler for allocation callstacks. Each time memory is allocated there is a chance a callstack will be collected. This information is tracked until deallocation. You can thus get information about what callstacks lead to the most live allocations, giving you a very useful memory profile of your running app, with minimal overhead.


Run-time memory tracking and profiling.

First steps

Add re_memory to your Cargo.toml:

cargo add re_memory

Install the AccountingAllocator in your main.rs:

use re_memory::AccountingAllocator;

static GLOBAL: AccountingAllocator<std::alloc::System>
    = AccountingAllocator::new(std::alloc::System);

Checking memory use

Use MemoryUse::capture to get the current memory use of your application.

Finding memory leaks

Turn on memory tracking at the top of your main() function:


Now let your app run for a while, and then call accounting_allocator::tracking_stats to get the statistics. Any memory leak should show up in TrackingStatistics::top_callstacks.


See also accounting_allocator.


~401K SLoC