Some context: - This has not shown up on manual nor automated testing on Linux x86-64. - `quinn-udp` has been introduced in https://bugzilla.mozilla.org/show_bug.cgi?id=1901295. - It is currently only enabled on Firefox Nightly. ```yml # Use NSPR for HTTP3 UDP IO - name: network.http.http3.use_nspr_for_io type: RelaxedAtomicBool # Always use NSPR on Android x86. On Android x86 sendmsg and recvmmsg, both used # by quinn-udp, are disallowed by seccomp. Future fix and further details # tracked in https://github.com/quinn-rs/quinn/issues/1947. #if defined(ANDROID) && !defined(HAVE_64BIT_BUILD) value: true #else value: @IS_NOT_NIGHTLY_BUILD@ #endif mirror: always ``` https://searchfox.org/mozilla-central/rev/03258de701dbcde998cfb07f75dce2b7d8fdbe20/modules/libpref/init/StaticPrefList.yaml#13590-13601 - Setting `network.http.http3.use_nspr_for_io` to `true` would prevent the Bug reported here. - This might be related to a previous seccomp failure on Android x86. - See Android x86 CI failure reported in https://bugzilla.mozilla.org/show_bug.cgi?id=1910594 - See upstream bug report https://github.com/quinn-rs/quinn/issues/1947. - See proposed solution upstream https://github.com/quinn-rs/quinn/pull/1964. I am new to Mozilla. Thus far I see [a total of 18 reports](https://crash-stats.mozilla.org/signature/?product=Firefox&signature=syscall%20%7C%20quinn_udp%3A%3Aimp%3A%3Arecvmmsg_with_fallback). Is this reason enough to role back the feature on Nightly, i.e. set `network.http.http3.use_nspr_for_io` to `true`?
Bug 1912626 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Some context: - This has not shown up on manual nor automated testing on Linux x86-64. - `quinn-udp` has been introduced in https://bugzilla.mozilla.org/show_bug.cgi?id=1901295. - The long term plan is to replace NSPR with `quinn-udp` for QUIC I/O. See https://bugzilla.mozilla.org/show_bug.cgi?id=1901292. - It is currently only enabled on Firefox Nightly. ```yml # Use NSPR for HTTP3 UDP IO - name: network.http.http3.use_nspr_for_io type: RelaxedAtomicBool # Always use NSPR on Android x86. On Android x86 sendmsg and recvmmsg, both used # by quinn-udp, are disallowed by seccomp. Future fix and further details # tracked in https://github.com/quinn-rs/quinn/issues/1947. #if defined(ANDROID) && !defined(HAVE_64BIT_BUILD) value: true #else value: @IS_NOT_NIGHTLY_BUILD@ #endif mirror: always ``` https://searchfox.org/mozilla-central/rev/03258de701dbcde998cfb07f75dce2b7d8fdbe20/modules/libpref/init/StaticPrefList.yaml#13590-13601 - Setting `network.http.http3.use_nspr_for_io` to `true` would prevent the Bug reported here. - This might be related to a previous seccomp failure on Android x86. - See Android x86 CI failure reported in https://bugzilla.mozilla.org/show_bug.cgi?id=1910594 - See upstream bug report https://github.com/quinn-rs/quinn/issues/1947. - See proposed solution upstream https://github.com/quinn-rs/quinn/pull/1964. I am new to Mozilla. Thus far I see [a total of 18 reports](https://crash-stats.mozilla.org/signature/?product=Firefox&signature=syscall%20%7C%20quinn_udp%3A%3Aimp%3A%3Arecvmmsg_with_fallback). Is this reason enough to role back the feature on Nightly, i.e. set `network.http.http3.use_nspr_for_io` to `true`?