WebTransport "pending" sessions

Demonstrates errored WebTransport sessions never leaving the "pending" state, even after five minutes.

Step 1

Open the developer console

Step 2

Open 50 WebTransport sessions to unresponsive or bad peers by clicking Connect

We expect these connections to fail.

In the list of errors that will appear below:

• "Opening handshake failed." means we connected successfully but could not verify the remote's certificate because it it self-signed
• "close() is called while connecting." means we took longer than 5s to connect so we closed the session
• "Connection lost." usually means Chrome has too many session in the "pending" state and is refusing to open new sessions

• Total: 0
• Success: 0
• Error: 0

Step 3

Wait for the countdown to end: 00:00

Step 4

Go back to step 2

After attempting to connect to another 50 peers you should not see a warning in the console about "Too many pending WebTransport sessions (64)"

If you do, errored WebTransport sessions are not leaving the "pending" state.

The source code for this page can be found at ipfs-shipyard/www-webtransport-pending-sessions