bug: large increase in memory usage over time with simple 2-node broadcast setup.

[benbot]

Describe the bug when running the "sim" binary in my repo (https://github.com/benbot/spaceronic/tree/weird-mem/rust/space-networking) after connecting 2 nodes, i see a constant increase in memory usage

Relevant Logs

Expected behavior memory doesn't balloon

Iroh

Version:

iroh v0.92.0
└── iroh-gossip v0.92.0 (/home/benbot/dev/iroh-gossip)
    ├── iroh-gossip feature "default"
    │   └── space-networking v0.1.0 (/home/benbot/gamedev/spaceronic/rust/space-networking)
    │       └── space-networking feature "default" (command-line)
    ├── iroh-gossip feature "metrics"
    │   └── iroh-gossip feature "default" (*)
    └── iroh-gossip feature "net"
        └── iroh-gossip feature "default" (*)
├── iroh feature "default"
│   └── space-networking v0.1.0 (/home/benbot/gamedev/spaceronic/rust/space-networking) (*)
├── iroh feature "discovery-local-network"
│   └── space-networking v0.1.0 (/home/benbot/gamedev/spaceronic/rust/space-networking) (*)
├── iroh feature "discovery-pkarr-dht"
│   └── space-networking v0.1.0 (/home/benbot/gamedev/spaceronic/rust/space-networking) (*)
└── iroh feature "metrics"
    └── iroh feature "default" (*)

Endpoint configuration:

no discovery or relay configured

Platform(s) Desktop:

• OS: Linux
• Version NixOS unstable

Additional Context / Screenshots / GIFs

here's the repo with the exact code i'm seeing this issue with: https://github.com/benbot/spaceronic/tree/weird-mem/rust/space-networking

for sanity's sake, i am running both instances on the same machine.

the repro steps are

1. cargo run and copy the ticket
2. in another terminal cargo run -- --ticket <ticket>
3. kill the 2nd instance
4. run cargo run -- --ticket <ticket> again (this is because i didn't want the hello messages sending on initial bootstrap)