Go-ipfs going out of memory

[lidel]

I feel this was already raised in:

IPFS daemon is eating up all the resources on my computer, what is happening?

I’m evaluating IPFS for more than a month now. It worked quite well initially, but nowadays things went crazy. Whenever I dare to start the daemon it will “spin up” within a hour and consumes 100% CPU, 3-4 GB RAM, and have 2040 peers connected, and the deamon cannot stop spewing error messages about “too many open files”. It’s started recently, what is happening?

go-ipfs team is actively working on improving the situation and testing it internally:

• tag kbucket peers for better connection closing by whyrusleeping · Pull Request #95 · libp2p/go-libp2p-kad-dht · GitHub
• tag 'can-hop' peers to aid in connection closing logic by whyrusleeping · Pull Request #20 · libp2p/go-libp2p-circuit · GitHub
• GitHub - libp2p/go-libp2p-connmgr: a resource sentinel that keeps connection count under reasonable bounds
• https://github.com/ipfs/go-ipfs/pull/4288

Hopefully it will be addressed in next release.