Summary of the conditions for the problem to occur and the outcome:

1. A "large" message must be being sent by both peers to each other contemporaneously (this condition can occur in some circumstances in IBD).
2. Where this occurs, both peers will "pause" receiving any socket buffer traffic until the full message is sent.
3. That message must be large enough to crash the TCP recive window on both sides (See Further Comments below).
4. Receiving would only be resumed when the message is sent - This condition never occurs because both sides crash the recv window before the full message can be sent (either way).
5. The connection at this point is inactive and effectively "hung" until the inactivity timeout kicks in and the connection is tinned.
6. It's entirely possible that after the connections is tinned, further/new connections have exactly the same issue (Further Comments Below).
7. A quick review of the Bitcoin Core 22.1.1 code base suggests that, conceptually, the problem exists there. If the relevant conditions hit, the bug should hit there, believe.

Further Comments:

1. "large" in this case isn't necessarily huge - depending on the network latency, TCP Windows Scaling and Windows values in play, a few hundred kilobytes should suffice.
2. Although the message is approximately 2Mb in Elements testing, only a few hundred kb are actually sent before the Windows are closed (see the attached tcpdump). TCP Window sizes are sub-100kb.
3. The application/message command line maxsendbuffer/maxrecvbuffer settings (and the related fPauseSend and fPauseRecv flags) are irrelevant to this issue - They can be set large, on both sides, and the problem will still occur. Setting them is not a workaround.

A bit of extra detail/markers:

1. A netstat -anp will reveal large, "stuck" Recv and Send Queues for the connection.

2. A tcpdump will show TCP Zero Windows on both sides of the connection - ie confirming that nothing is being pulled off the receive buffers (See attached example).

3. Testing simply requires hitting the conditions described above. Factors that may make the issue more likely are:

   • Increasing the network latency of the connection (eg using netem).
   • Reducing the TCP Window Scale Factor (or disabling TCP Window Scaling).

Expected behavior
The viable TCP Connection is maintained (data is read from the socket receive buffer on at least one side of the connection to relieve the stall)

Actual behavior
The connection is "stalled" until the inactivity timeout is reached, when the connection is closed (but on re-establishment with the same client, it's entirely likely the issue may recur - See to reproduce below).

To reproduce
See comments above. The issue can be difficult to reproduce. One approach using release builds is to:

1. Have a "client" approximately 1200 blocks behind the liquidv1 chain.
2. Ensure high network latency between the client and a single configured peer to sync to (eg use netem to simulate ~150ms latency)
3. Launch the client to proceed with IBD.

Note that this is one concrete example of the issue. The problem appears general.

System information
Tested/Reproduced on Elements versions 21.0.2 - 22.1.1
OSes = Centos 8, Unbuntu 22.0.4

Extra Information
Example debug log snippet (Elements 21.0.2 Release Build):

2022-09-16T14:53:53Z Added connection peer=0
2022-09-16T14:53:53Z sending version (110 bytes) peer=0
2022-09-16T14:53:53Z send version message: version 70016, blocks=2009311, us=[::]:0, peer=0
2022-09-16T14:53:54Z received: version (110 bytes) peer=0
2022-09-16T14:53:54Z sending wtxidrelay (0 bytes) peer=0
2022-09-16T14:53:54Z sending sendaddrv2 (0 bytes) peer=0
2022-09-16T14:53:54Z sending verack (0 bytes) peer=0
2022-09-16T14:53:54Z Leaving InitialBlockDownload (latching to false)
2022-09-16T14:53:54Z ProcessMessages: advertising address 188.29.65.218:7042
2022-09-16T14:53:54Z sending getaddr (0 bytes) peer=0
2022-09-16T14:53:54Z receive version message: /Elements Core:0.21.0.2/: version 70016, blocks=2010501, us=188.29.65.218:35788, peer=0
2022-09-16T14:53:54Z added time data, samples 2, offset +0 (+0 minutes)
2022-09-16T14:53:54Z received: wtxidrelay (0 bytes) peer=0
2022-09-16T14:53:54Z received: sendaddrv2 (0 bytes) peer=0
2022-09-16T14:53:54Z received: verack (0 bytes) peer=0
2022-09-16T14:53:54Z New outbound peer connected: version: 70016, blocks=2010501, peer=0 (full-relay)
2022-09-16T14:53:54Z sending sendheaders (0 bytes) peer=0
2022-09-16T14:53:54Z sending sendcmpct (9 bytes) peer=0
2022-09-16T14:53:54Z sending sendcmpct (9 bytes) peer=0
2022-09-16T14:53:54Z sending ping (8 bytes) peer=0
2022-09-16T14:53:54Z AdvertiseLocal: advertising address 188.29.65.218:7042
2022-09-16T14:53:54Z sending addrv2 (16 bytes) peer=0
2022-09-16T14:53:54Z initial getheaders (2009310) to peer=0 (startheight:2010501)
2022-09-16T14:53:54Z sending getheaders (1061 bytes) peer=0
2022-09-16T14:53:54Z sending feefilter (8 bytes) peer=0
2022-09-16T14:53:54Z received: sendheaders (0 bytes) peer=0
2022-09-16T14:53:54Z received: sendcmpct (9 bytes) peer=0
2022-09-16T14:53:54Z received: sendcmpct (9 bytes) peer=0
2022-09-16T14:53:54Z received: ping (8 bytes) peer=0
2022-09-16T14:53:54Z sending pong (8 bytes) peer=0
2022-09-16T14:53:54Z received: addrv2 (16 bytes) peer=0
2022-09-16T14:53:54Z received: getheaders (1061 bytes) peer=0
2022-09-16T14:53:54Z getheaders 2008444 to end from peer=0
2022-09-16T14:53:54Z sending headers (1272026 bytes) peer=0
2022-09-16T14:53:54Z tor: Error connecting to Tor control socket
2022-09-16T14:53:54Z tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect

The connection is "stalled" at this point,.

Example pcap file (from a different execution / on Elements 22.1.1) - Shows TCP Windows crashing each side.

ElementsTCPWindowStall.zip

The key code is GenerateSelectSet and SocketSendData.