You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently debugging the issue described in quic-go/quic-go#4712. The problem is with the interjection of QUIC and libp2p, and where exactly the culprit is still needs to be discovered. What is known is that the issue is only present on both QUIC/WT, but does not exist on TCP.
The TLDR is that there is a disconnect between QUIC and libp2p stream closing. While libp2p considers a stream closed, the QUIC stack still keeps it around, eventually deadlocking once the stream limit is reached.
I am currently debugging the issue described in quic-go/quic-go#4712. The problem is with the interjection of QUIC and libp2p, and where exactly the culprit is still needs to be discovered. What is known is that the issue is only present on both QUIC/WT, but does not exist on TCP.
The TLDR is that there is a disconnect between QUIC and libp2p stream closing. While libp2p considers a stream closed, the QUIC stack still keeps it around, eventually deadlocking once the stream limit is reached.
Version Information
The text was updated successfully, but these errors were encountered: