Bizarre memory leak caused by tokio runtime

• jemallocator

  3 366 5.9 Rust

  Rust allocator using jemalloc as a backend (by tikv)

  

  I was able to replicate the issue with the sample code, but not when using a different allocator (https://github.com/tikv/jemallocator). I understand the default allocator on Linux is malloc (https://doc.rust-lang.org/std/alloc/struct.System.html), and while looking up the differences between the two, it seems like jemalloc handles memory fragmentation much better (https://engineering.linkedin.com/blog/2021/taming-memory-fragmentation-in-venice-with-jemalloc). Maybe that's what's going on?

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• tokio

  211 27,258 9.5 Rust

  A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

  

  This link specifically has more info on why the memory could creep up when you spawn a lot of tasks.

• Mesh

  6 1,756 6.3 C++

  A memory allocator that automatically reduces the memory footprint of C/C++ applications.

  

  With everyone talking about memory fragmentation, I'd like to mention Mesh, an allocator that can compact aka defrag the heap without any help from the program or compiler. Here's the talk explaining it, "Compacting the Uncompactable" by Bobby Powers.

• rkyv

  13 2,981 9.4 Rust

  Zero-copy deserialization framework for Rust

  

  I had the same problem when trying to deserialize a big struct with rkyv: see rkyv#277.

Suggest a related project