Failing to run on binaries created by bevy

[TotalKrill]

Hello, wrote on the reddit post as well.

Reproduce

Trying to run this on bevy crates fails, i have not tested it very thoroughly, but to reproduce you could:

git clone https://github.com/bevyengine/bevy.git
cd bevy
cargo build --example 3d_scene
allocscope-trace target/debug/example/3d_scene

expected behaviour

A 3d scene with a box should show up, standing still, nothing else, quitting the software will stop the process, and the atrace can be inspected.

actual behaviour

the 3D scene will not show up, and allocscope-trace will say and show nothing. ctrl+c will quit it though
running it for a while will create an atrace file though, and that can be inspected ( sometimes crash, but not easily reproduced, said something about higher number? dont remember )

[matt-kimball]

The issue seems to be that allocscope is slowing down the traced process so much that it is not very usable. I do get a window after several minutes, and if I press ctrl+c to terminate the trace, I get an .atrace which does show Bevy things happening.

I intend to rework the mechanism of tracing to speed things in the near future. I expect that tracing a Bevy process will improve when that work is complete.