fix: use mimalloc on Linux to mitigate "memory leak"

XOR-op · Jul 6, 2024 · 4ae308a · 4ae308a
1 parent b254513
commit 4ae308a
Show file tree

Hide file tree

Showing 3 changed files with 29 additions and 0 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/boltconn/Cargo.toml b/boltconn/Cargo.toml
@@ -96,6 +96,7 @@ netlink-sys = "0.8.3"
 netlink-packet-core = "0.5.0"
 netlink-packet-sock-diag = "0.4.0"
 procfs = "0.16.0"
+mimalloc = "0.1.43"
 
 [dev-dependencies]
 tracing-test = "0.2.4"
diff --git a/boltconn/src/main.rs b/boltconn/src/main.rs
@@ -27,6 +27,14 @@ mod platform;
 mod proxy;
 mod transport;
 
+// System default allocator (glibc) won't reclaim freed memory actively on Linux.
+// Without enough SWAP and RAM, this may cause OOM. Use MiMalloc to mitigate this issue.
+#[cfg(target_os = "linux")]
+use mimalloc::MiMalloc;
+#[cfg(target_os = "linux")]
+#[global_allocator]
+static GLOBAL: MiMalloc = MiMalloc;
+
 #[derive(Debug, Parser)]
 #[clap(name = "boltconn", about = "CLI interface of BoltConn", version = env!("CARGO_PKG_VERSION"))]
 struct ProgramArgs {