Fix Memory Leak - Githubissues

cabal-club / commons

high level thoughts and issues for the future of cabal

14 stars 2 forks source link

Open cblgh opened 4 years ago

cblgh commented 4 years ago

People using cabal-cli have been running into ENOMEM
ENOMEM occurs more frequently in larger cabals, than in smaller cabals (but with more messages)
mafintosh says hypercore & hyperswarm do not have any known memory leaks
cabal-client is a good first place to look at, esp peering & listeners

cblgh commented 3 years ago

https://github.com/kappa-db/multifeed/pull/49 went a long way towards mitigating the issue!

as per my comment, down the PR thread, we're still leaking a couple of hundred kB per minute