[Bug]: send stream packet 1Mbps get drop rate, the stream is unreliability and unstability

[leopard2ic]

What happened?

1 Forward or schedule packet to xquic, send stream packet use function bellow
void client_network_send(void *out_data, size_t out_dlen) {
g_user_stream->send_body = out_data;
g_user_stream->send_body_len = out_dlen;
g_user_stream->send_offset = 0;
client_stream_send(g_user_stream->stream, g_user_stream);
}

2 Send iperf udp packet in limited bandwidth and get the packet lost

iperf -u -c 10.7.0.1 -b 1M -t 10 -p 6001 // drop rate 20%
iperf -u -c 10.7.0.1 -b 2M -t 10 -p 6001 // drop rate 50%

3 The stream transport is unreliability and unstability
3.1 server stream segmentation fault

3.2 server close stream actively

3.3 client stream segmentation fault

Steps To Reproduce

1 Forward or schedule packet to xquic
2 send packet with function client_network_send( )
3 use iperf test tool to detect the udp throughput
4 get some drop rate and unstability

Relevant log output

No response

[leopard2ic]

iperf.zip

[Kulsk]

iperf.zip

your keys are invalid, none of the 1-RTT packets could be decrypted, make sure it's available plz

[leopard2ic]

Quic packet is captured on client physical network interface, use ckeys.log ?

[Kulsk]

Quic packet is captured on client physical network interface, use ckeys.log ?

never worked, maybe you should try to parse the pcap with wireshark on your local machine before upload it

[Kulsk]

is no_encrypt used ?

[Kulsk]

I tried to grep '====>' on clog and slog, it seems packets numbers are sequential and consistent, none is lost on server rx side

[leopard2ic]

capture file have two steps,
1> 1m udp, clog to 679, slog to 679
2> 2m udp, clog to 197, slog to 154