about:networking#sockets UDP Sent and Received is 0 with network.http.http3.use_nspr_for_io false
Categories
(Core :: Networking, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox129 | --- | unaffected |
firefox130 | --- | disabled |
firefox131 | --- | fixed |
People
(Reporter: mail, Assigned: mail)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [necko-triaged])
Attachments
(1 file)
When Nightly only network.http.http3.use_nspr_for_io
is set to false
then about:networking#sockets
Sent
and Received
is 0
for UDP
for HTTP/3 QUIC UDP sockets.
Note that network.http.http3.use_nspr_for_io
is only set to false
on Firefox Nightly. Thus this regression only affects Firefox Nightly.
I will follow-up with a patch in a bit.
An nsIUDPSocket
tracks the number of bytes sent and received through its
methods, e.g. RecvWithAddr
. The number of bytes is then displayed in
about:networking#sockets.
With network.http.http3.use_nspr_for_io
set to false
Http3Session
uses
quinn-udp
instead of NSPR
for HTTP/3 QUIC UDP IO. Thus it does not use
nsIUDPSocket
RecvWithAddr
, but instead optains a raw file descriptor via
nsIUDPSocket
GetFileDescriptor
and then does its IO directly. Thereby the
number of bytes sent and received in nsIUDPSocket
are not updated, i.e. stay
at 0
.
This commit exposes two new methods in nsIUDPSocket
, namely addOutputBytes
and addInputBytes
which are each called after any IO operation on the raw file
descriptor optained through nsIUDPSocket
GetFileDescriptor
.
Updated•2 months ago
|
Comment 3•2 months ago
|
||
Set release status flags based on info from the regressing bug 1901295
Updated•2 months ago
|
Comment 5•2 months ago
|
||
bugherder |
Description
•