If it exists, any possibilities to turn on or turn off it.

Better and funniest description for the crate which was ever made!

Since GlobalHeap can be created from an arbitrary pointer, and code assumes heaps always have valid pointers, it is easy to cause UB:

use mimalloc_rust::heap::GlobalHeap;
use mimalloc_rust::heap::MiMallocHeap;
use mimalloc_rust::*;

#[global_allocator]
static GLOBAL_MIMALLOC: GlobalMiMalloc = GlobalMiMalloc;

fn main() {
    let new_heap = GlobalHeap {
        heap: std::ptr::null_mut(),
    };

    GlobalMiMalloc::replace_by(&MiMallocHeap::new(new_heap));
 }

Hi, thank you for building this library.

I'm using this library for the swc project (https://swc.rs)

Someone reported memory error on windows 11, and https://github.com/microsoft/mimalloc#releases says it's fixed on 1.7.5
I read the source code and seems like this crate is using 1.7.3

This crate is nightly-only, but it's not stated in the ReadMe nor the main documentation (lib.rs does this). Many users use stable Rust release, and this crate should be usable in stable environment, albeit with missing features (e.g. Allocator API) instead of being completely unable to compile at all.

Solution

Guard Allocator API usage behind a feature gate, and release a stable version with the Allocator trait items implemented without specifying the trait.

Alternative solution

Write 🚧🚧🚧 This crate is Nightly Only 🚧🚧🚧 in readme.