> Our current suspicion is that Google Cloud Load Balancer (or a similar CloudFlare service) that fronts one of our own servers got an update that triggers an existing HTTP3 bug. Telemetry was first implicated because it's one of the first services a normal Firefox configuration will connect first, but presumably the bug will trigger with any other connection to such a server. Our current plan is to disable HTTP3 to mitigate until we can locate the exact bug in the networking stack.
No, it's not required to start. Without the bug firefox starts up just fine (in fact, if google's servers were to drop off the internet, the problem would also go away). The problem is the bug hangs all network communication when it's triggered.
> We have other services with the same type of load balancer in front of it and we currently suspect it is an HTTP/3 load balancing problem.
https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17
> Our current suspicion is that Google Cloud Load Balancer (or a similar CloudFlare service) that fronts one of our own servers got an update that triggers an existing HTTP3 bug. Telemetry was first implicated because it's one of the first services a normal Firefox configuration will connect first, but presumably the bug will trigger with any other connection to such a server. Our current plan is to disable HTTP3 to mitigate until we can locate the exact bug in the networking stack.
https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21