Investigate codebase for memory problems

[qdm12]

This is more of low hanging fruits that can be worth checking/fixing before investing more time in profiling and metrics, to fix the current memory issue we have (2021-11-03).

• [x] Check usage of bytes.Buffer (local branch)
• [x] Check usage of pools
• [ ] Check usage of copy
• [ ] Check buffered channels (using regex make\(chan .+, [1-9].+\))
• [x] Check DeepCopy functions (search for deepcopy without case sensitivity)
• [x] Check usage of sizedBufferPool - found a problem, fixed in #1963, although not a reason for OOM
• [ ] Check for arrays returned (copy, it's not a slice), use regex \[[a-zA-Z0-9]+\](byte|int|uint|uint32|uint64|int32|int64|string)+?
• [ ] Check packages
  • [ ] dot/network
  • [x] lib/trie
  • [ ] dot/sync

[qdm12]

The current state as of today is:

• the trie works fine and does not leak (probably thanks to #2929 and #2919)
• Node running the Kusama chain does not cleanup tries in the in-memory map of tries after syncing 1.5M blocks
• Node running the Polkadot chain seems to use ~10MB per day of sync (= ~1M blocks) so that should be fine
• On the polkadot chain, leaks now come from the badgerdb implementation (see #2982) and the hashToRuntime map (see #2767)