Skip to content

Fix false QUIC flow-control errors during bulk downloads - #153

Merged
andre487 merged 1 commit into
mainfrom
fix/quic-advertised-flow-control
Nov 21, 2026
Merged

andre487 merged 1 commit into
mainfrom
fix/quic-advertised-flow-control

Conversation

@andre487

@andre487 andre487 commented Nov 21, 2026 •

Copy link
Copy Markdown
Owner

Browser QUIC fingerprints advertise receive credit that differs from quic-go defaults. Chrome permits 6 MiB per stream while the runtime initially allowed 512 KiB, so a compliant server could trigger a local FLOW_CONTROL_ERROR and close every stream in the session, including iperf3's control connection.

Initialize flow control from the actual uTLS transport parameters before connection setup, preserving distinct local/remote bidirectional and unidirectional limits and connection credit. Ordinary connections retain configured windows. Browser wire parameters are unchanged and excess data is still rejected.

Validation: deterministic boundary regression failed for all four advertised-credit cases before the fix and passes afterward; a 32 MiB download verifies payload integrity and a surviving control stream for Chrome, Firefox and randomized profiles. bundle exec fastlane android native_tests passes all 370 tests with the race detector. On the isolated Linux VM, the original HTTP/3 reverse failure reproduces with explicit FLOW_CONTROL_ERROR; the instrumented fixed helper passes three reverse samples using the same iperf3 3.16, with three sing-box controls also passing. The same fixed helper passes all six MASQUE reverse cases (three samples, one/eight streams), and all six corresponding sing-box controls pass. These VM controls use the original iperf3 3.16 to isolate the QUIC fix. Diagnostic figures are not new performance claims. Android/device execution remains CI coverage, not a completed local check.

Discovered while investigating comparison PR #152. The separate sing-box nested-QUIC DATAGRAM-size failure and old iperf3 segfault are not fixed by this patch.

APK artifacts

Built from commit f7e6523c by CI run #492.
Artifacts expire after 14 days. Neither APK uses the MegaProxy release key.

@andre487
andre487 merged commit bf8ecae into main Nov 21, 2026
15 checks passed
@andre487
andre487 deleted the fix/quic-advertised-flow-control branch November 21, 2026 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant