Open lexnv opened 4 hours ago
Similar to https://github.com/paritytech/litep2p/issues/269, the state tracking around canceling dials is monotonically increasing:
The AbortableHandler logic was introduced on top of the cancellation by connection ID, therefore I expect the fix to be similar for both cases.
AbortableHandler
cc @paritytech/networking
The cancel by abort handler is not yet merged, therefore the leak might come entirely from the "cancel by connection ID"
Similar to https://github.com/paritytech/litep2p/issues/269, the state tracking around canceling dials is monotonically increasing:
The
AbortableHandler
logic was introduced on top of the cancellation by connection ID, therefore I expect the fix to be similar for both cases.TCP
WebSocket
cc @paritytech/networking