I would recommend trying to minimize it further. The repro currently depends on 6 crates. Minimizing it down to 1 or 0 would make it clearer where to look for the leak.
================= Iteration 1
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
8f0a4a2620d3 naughty_stonebraker 0.06% 2.043MiB / 1.952GiB 0.10% 3.01MB / 7.88kB 0B / 0B 28
================= Iteration 2
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
8f0a4a2620d3 naughty_stonebraker 0.04% 2.105MiB / 1.952GiB 0.11% 6.02MB / 15.6kB 0B / 0B 28
================= Iteration 3
CONTAINER ID NAME CPU % MEM USAGE / LIMIT
...
================= Iteration 27
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
8f0a4a2620d3 naughty_stonebraker 0.05% 1.949MiB / 1.952GiB 0.10% 81.3MB / 240kB 0B / 0B 28
================= Iteration 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
8f0a4a2620d3 naughty_stonebraker 0.05% 1.934MiB / 1.952GiB 0.10% 84.3MB / 250kB 0B / 0B 28
================= Iteration 29
CONTAINER ID NAME CPU % MEM USAGE / LIMIT
leaks with default allocator
================= Iteration 1
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
ee83ae7ec901 angry_mahavira 0.04% 14.27MiB / 1.952GiB 0.71% 3.01MB / 7.81kB 0B / 0B 28
================= Iteration 2
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
ee83ae7ec901 angry_mahavira 0.05% 20.53MiB / 1.952GiB 1.03% 6.02MB / 17.2kB 0B / 0B 28
================= Iteration 3
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM %
...
================= Iteration 19
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
ee83ae7ec901 angry_mahavira 0.07% 56.8MiB / 1.952GiB 2.84% 57.2MB / 167kB 0B / 0B 28
================= Iteration 20
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
ee83ae7ec901 angry_mahavira 0.04% 57.43MiB / 1.952GiB 2.87% 60.2MB / 175kB 0B / 0B 28
================= Iteration 21
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM %