NTCP V2 inbound conns starved

[jogger]

Seeing some inbound NTCP V2 conns starved after receiving a single sent with outgoing packets piling up in the queue. Those stay indefinitely on the /peers page with queued packets going up over time.

Like this:

RU 0hMe Inbound 2 36 min / 36 min 0,00 / 0,00 36 min 1000 ms 1 0 1

[jogger]

Similar effect for outbound, but those go into backlogged and finally disappear:

WARN [ GW pumper 2] .transport.ntcp.NTCPConnection: Too backlogged: size is 512, wantsWrite? true, currentOut set? true, id: 51, writeBufs: 1 on NTCP2 conn 13139 to 41.68.199.192 port 29151 kI833f created 5m ago, last send 5m ago, last recv 5m ago, sent 49, rcvd 1

[jogger]

Now have this seen also for V1 inbound. Most extreme case, marked as backlogged for hours on /peers:

?? 0hMe Inbound 2 6 hours / 6 hours 0,00 / 0,00 6 hours 1000 ms 1 0 340 ✔

for this conn I found this log 6 hours old:

WARN [P reader ½] .transport.ntcp.NTCPConnection: Old connection closed: NTCP2 conn 920 to 84.201.142.19 port 21608 0hMeZN created 1289ms ago, last send 40ms ago, last recv 1289ms ago, sent 3, rcvd 1 replaced by NTCP2 conn 924 from /84.201.142.19 port 61816 0hMeZN created 175ms ago, last send 175ms ago, last recv 175ms ago, sent 1, rcvd 0