Using a global_allocator with rules_rust

[DolceTriade]

Hello!

Has anyone successfully compiled using a global allocator (jemalloc) using bazel?

I was trying to figure out why jemalloc didn't see any allocations until I dug into rules_rust and found that it doesn't handle #[global_allocator] the same way as regular rust.

I have a hobby (OSS) BEP visualization app I'm trying to improve to find some memory leaks and was hoping to utilize jemalloc to do so. But it's a weird app in that its compiled both to a native target and to wasm using Leptos. So I want the native version to use a custom global allocator but not the wasm stuff (which has the same code with slightly different features).

However, when I try to enable experimental_use_cc_common_link, I start getting a bunch of undefined references:

bazel-out/k8-fastbuild-ST-883eaf4958dc/bin/blade/bep/libbep-746419035.a(bep-746419035.bep.8897bd54eb3b6671-cgu.10.rcgu.o):bep.8897bd54eb3b6671-cgu.10:function <failure_details_proto::failure_details::Analysis as prost::message::Message>::encoded_len:(.text._ZN92_$LT$failure_details_proto..failure_details..Analysis$u20$as$u20$prost..message..Message$GT$11encoded_len17h7db7e003c699dea4E+0x11): error: undefined reference to '<failure_details_proto::failure_details::analysis::Code as core::default::Default>::default'
bazel-out/k8-fastbuild-ST-883eaf4958dc/bin/blade/bep/libbep-746419035.a(bep-746419035.bep.8897bd54eb3b6671-cgu.10.rcgu.o):bep.8897bd54eb3b6671-cgu.10:function <failure_details_proto::failure_details::Execution as prost::message::Message>::encode_raw:(.text._ZN93_$LT$failure_details_proto..failure_details..Execution$u20$as$u20$prost..message..Message$GT$10encode_raw17hecfc8187bb6ac95dE+0x15): error: undefined reference to '<failure_details_proto::failure_details::execution::Code as core::default::Default>::default'

(Here is a small snippet but there are a lot. Most of them seem to be prost related, so I'm hoping that if I resolve the prost related ones, I can make more progress.

One thing I notice is that the .a prost libraries created with rust_prost_library do not seem to make it to the final binary in the link params if they are a transitive dependency of the final binary. (That said, forcibly making them a dependency of the final binary does not seem to help either).

Is this expected behavior and I need to do more to work around this issue?