We observed that the 32-bit test runner runs out of memory if we increase the test count to 100.
There are two areas where we leak goroutines after the test has stopped:
leveldb has a one-second delay before properly releasing all resources. There is nothing immediate we can do about that. If we added a delay of 1s + δ, all resources are released.
Migrated from https://github.com/libp2p/go-libp2p-kad-dht/issues/906
We observed that the 32-bit test runner runs out of memory if we increase the test count to
100
.There are two areas where we leak goroutines after the test has stopped:
Revisit after https://github.com/libp2p/go-libp2p/issues/2514 has been resolved.