This issue is very similar to https://github.com/nymtech/nym/issues/424 as it also refers to cleaning up stale data. However, this can apply to both socks5 client and network requester.
Both socks5 client and network requester keep track of ids of all 'recently' closed connections and messages received out of order (not to be confused with OrderedMessage. this ONLY refers to receiving 'Send' before a 'Connect'). However, that data is NEVER cleared meaning that at some point we can simply run out of memory. Also it can be relatively easily abused...
This issue is very similar to https://github.com/nymtech/nym/issues/424 as it also refers to cleaning up stale data. However, this can apply to both socks5 client and network requester.
Both socks5 client and network requester keep track of ids of all 'recently' closed connections and messages received out of order (not to be confused with
OrderedMessage
. this ONLY refers to receiving 'Send' before a 'Connect'). However, that data is NEVER cleared meaning that at some point we can simply run out of memory. Also it can be relatively easily abused...