joshuef

@thomaseizinger within this PR there are no `clone` sites, but outwith [there](https://github.com/libp2p/rust-libp2p/blob/master/protocols/gossipsub/src/behaviour.rs#L795) [are some `RawMessage` `clone`s](https://github.com/libp2p/rust-libp2p/blob/master/protocols/gossipsub/src/behaviour.rs#L630) that otherwise [will duplicate the entire `data` field](https://github.com/libp2p/rust-libp2p/blob/master/protocols/gossipsub/src/behaviour.rs#L657) there. It also helps prevent /...

> Looking in more detail at the code and this screenshots Ah right, yeh I was just focussing on the gossip allocations there. You have the two heaptracks entirely in...

Also, I was just poking about quick-protobuf w/r/t `Bytes`, but I dont think it makes sense there. The generated code would require that the consuming app was having a `Bytes`...

it seems we had two relay events around the panic time: ```[2024-05-20T07:07:36.427103Z INFO sn_networking::event::swarm] relay client event event=OutboundCircuitEstablished { relay_peer_id: PeerId("12D3KooWDEyeJJP5eFJocmeu874u8YE4UwvqXtz5ewvKLuzKbFKT"), limit: None } [2024-05-20T07:07:36.488761Z INFO sn_networking::event::swarm] relay client event...