dashmap VS cargo-flamegraph

The problem is, every single one of these half-dozen crates has at least one known major issue (including UAF), exactly like C++ implementations (which isn't surprising since it's the kind of things where the ownership isn't clear and then the borrow checker can't help us).

Deadlocks and leaks are easy as other languages.

Have you considered https://github.com/xacrimon/dashmap ?

Dashmap made some api changes compared to the stdlibs hashmap, which leads to some oddities, as highlighted here: https://github.com/xacrimon/dashmap/issues/175

Some additional notes are in this slide deck and the implementation javadoc. You'd probably want to use something like DashMap for the hash table.

You can look at existing concurrent maps like Dashmap https://github.com/xacrimon/dashmap or Cashmap https://gitlab.redox-os.org/redox-os/chashmap

Also dashmap

The only one I've used is Dashmap, it's a concurrent interior-mutability hashmap. Very convenient crate in the case you need that.

I'd suggest cargo flamegraph https://github.com/killercup/cargo-flamegraph

Check out cargo flamegraph.

cargo-flamegraph is a very simple and portable tool to understand where the time is spent in your application. If you want more detailed info, try this: perf record -g --call-graph=dwarf /path/to/your/application and then load it into Firefox Profiler. That's the best profiling UI available.