4 ms·

It seems another workaround is disabling the collection of usage data: https://twitter.com/vanilla_chief/status/1481546294489489409 https://twitter.com/vanilla

It seems another workaround is disabling the collection of usage data: https://twitter.com/vanilla_chief/status/1481546294489489409 https://twitter.com/vanilla_chief/status/1481546294489489409 €: It seems telemetry does no longer triggers the bug as they've changed something on the server side? So this probably won't help anymore.

tpm 5y ago
this worked for me too
jml7c5 5y ago
Can confirm this worked.
mftb 5y ago
I already had that disabled when it struck me.
- jacquesm 5y ago
  I had too but it mysteriously re-enabled on all FF instances on various laptops and desktops here. I wonder when that happened.
- jabiko 5y ago
  The current theory is that some CDN/LoadBalancer updated its HTTP3 implementation and is now triggering a bug in the HTTP3 stack of Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 It just happens that the usage data collection uses that CDN thus triggering the bug. But you can also encounter it by just visiting any other website served by that CDN.
duncanc4 5y ago
This worked. Funny that this bug will cause people to turn off the opt-out data collection. No one is going to turn it back on after the issue is fixed.
- jacquesm 5y ago
  Don't worry, FF will do an automatic update to re-enable it. Again. Without your consent.
- mardifoufs 5y ago
  They will turn it back on for you. I could swear I've had it turned off a few times already before, and I'm definitely sure I did it at least once yet here we are :). Telemetry in itself isn't the end of the world, but disregarding the settings your users chose is such a weird behavior coming from an organization that pretends to care about choice.
terom 5y ago
https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 telemetry is not the only service affected, it's advisable to disable http3 entirely as a workaround for now

tpm 5y ago

this worked for me too

jml7c5 5y ago

Can confirm this worked.

mftb 5y ago

I already had that disabled when it struck me.

jacquesm 5y ago
I had too but it mysteriously re-enabled on all FF instances on various laptops and desktops here. I wonder when that happened.
jabiko 5y ago
The current theory is that some CDN/LoadBalancer updated its HTTP3 implementation and is now triggering a bug in the HTTP3 stack of Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 It just happens that the usage data collection uses that CDN thus triggering the bug. But you can also encounter it by just visiting any other website served by that CDN.

duncanc4 5y ago

This worked. Funny that this bug will cause people to turn off the opt-out data collection. No one is going to turn it back on after the issue is fixed.

jacquesm 5y ago
Don't worry, FF will do an automatic update to re-enable it. Again. Without your consent.
mardifoufs 5y ago
They will turn it back on for you. I could swear I've had it turned off a few times already before, and I'm definitely sure I did it at least once yet here we are :). Telemetry in itself isn't the end of the world, but disregarding the settings your users chose is such a weird behavior coming from an organization that pretends to care about choice.

terom 5y ago

https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 telemetry is not the only service affected, it's advisable to disable http3 entirely as a workaround for now