Peer with no streams but maxed out memory

[BigLep]

Impact: this is blocking enabling the resource mananager on by default in Lotus.

Context is in Filecoin slack: https://filecoinproject.slack.com/archives/CP50PPW2X/p1649118410337389

"12D3KooWQ4fdNGJb92npgJQsdjE8XS4Cgy8mLwnBrmePfAASYPdH": {
      "NumStreamsInbound": 0,
      "NumStreamsOutbound": 0,
      "NumConnsInbound": 1,
      "NumConnsOutbound": 0,
      "NumFD": 1,
      "Memory": 67108864
    },

With logs like

2022-04-05T02:25:30.547+0200    DEBUG   rcmgr   go-libp2p-resource-manager@v0.1.5/scope.go:242  blocked memory reservation      {"scope": "peer:12D3KooWQ4fdNGJb92npgJQsdjE8XS4Cgy8mLwnBrmePfAASYPdH", "size": 262144, "priority": 255, "stat": {"NumStreamsInbound":0,"NumStreamsOutbound":1,"NumConnsInbound":2,"NumConnsOutbound":0,"NumFD":2,"Memory":67108864}, "error": "resource limit exceeded"}

[BigLep]

From @vyzo (in slack):

seems like a bug in the muxer, not releasing memory
but maybe its a QUIC conn
i think the rcmgr itself is totally fine