You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I took an existing program, added a dependency on jemallocator-global in its Cargo.toml, built it with --release, and ran it under a profiler (Instruments). Observed: The profiler found stacks under libsystem_malloc.dylib. Expected: stacks under a statically linked jemalloc.
Depending directly on the jemallocator crate instead, and declaring a #[global_allocator] static Jemalloc in the binary crate, works fine.
I'm using stable Rust 1.37: rustc 1.37.0 (eae3437df 2019-08-13)
The text was updated successfully, but these errors were encountered:
@jorendorff we can probably add #[used] here to work around this, could you give it a try and see if adding #[used] to the jemallocator-global crate fixes this ?
I took an existing program, added a dependency on
jemallocator-global
in its Cargo.toml, built it with--release
, and ran it under a profiler (Instruments). Observed: The profiler found stacks under libsystem_malloc.dylib. Expected: stacks under a statically linked jemalloc.Depending directly on the
jemallocator
crate instead, and declaring a#[global_allocator]
staticJemalloc
in the binary crate, works fine.I'm using stable Rust 1.37:
rustc 1.37.0 (eae3437df 2019-08-13)
The text was updated successfully, but these errors were encountered: