Follow

PSA: If your firefox browser suddenly starts consuming 100% of a CPU core and doesn't seem to load pages anymore, go to about:config, search for the key "network.http.http3.enabled" and set it to false

They just pushed the most vile and foul update and it broke everything

really excited to read about the postmortem of this one

@ShadyFennec "Thanks Kevin, but currently millions of people need to use their browser ..." yeah that's something mozilla needs to understand ASAP...

Firefox was crashing on me randomly the whole of last week, like I'd leave the computer be for a while and come back to a crashed firefox, worrying about all my tabs. this explains it, thank you.

@cadadr @ShadyFennec but this bug causes it to hang, not to crash?

On the other hand it explains my experience of the last half a year...

@ShadyFennec i've been distrustful of HTTP/2 since its inception, and then some more of HTTP/3

@clacke @ShadyFennec let's implement TCP over HTTP

you know who's best at doing this?
giant companies who are the only ones dictating the new standards, and the only ones actually remotely benefiting from it, due to their sheer scale

also the only ones who could push thru a new standard replacing TCP, or a new protocol replacing / supplementing HTTP that runs on a different Port, but, nope, they chose their power to fuck up a perfectly adequate* protocol instead.

____
*lest i be misinterpreted: HTTP is not good, not great, it's just that: adequate

@meena @ShadyFennec > let's implement TCP over HTTP

That doesn't seem like a fair and factual description.

> a new standard replacing TCP

Arguably they kind of did that.

> or a new protocol replacing / supplementing HTTP that runs on a different Port

HTTP/3 replaces/supplements HTTP/1.1 on a different protocol_number/port pair.

> fuck up a perfectly adequate* protocol instead

I've seen more people than you say this. Clearly it introduces new complexity and mistakes to be made, as it introduces more slightly different ways for data to reach the browser.

@clacke

a new standard replacing TCP

Arguably they kind of did that.

not if every application has to implement it

how many applications implement their own TCP?

or a new protocol replacing / supplementing HTTP that runs on a different Port

HTTP/3 replaces/supplements HTTP/1.1 on a different protocol_number/port pair.

which?

fuck up a perfectly adequate* protocol instead

I've seen more people than you say this. Clearly it introduces new complexity and mistakes to be made, as it introduces more slightly different ways for data to reach the browser.

The fact that the browser is the only applications even considered in a whole new protocol is so unambitious and boring, i could cry

@ShadyFennec @IceWolf Lol, Firefox's data collection is the one thing triggering the bug.

@ShadyFennec .hg The Bugzilla thread warns that that's a temporary workaround that will break something else in the future, so…if you do this then don't forget to undo it a week from now.

@ShadyFennec getting some real WTF vibes, looked up HTTP3 & it's HTTP over UDP, aka "we don't care if half your data doesn't get there"

@ShadyFennec

AH.

That explains why everything locked up on me, last night... thank you!

@ShadyFennec is that what that was. Mozilla sure are keen on me switching to Chrome.

@Jnetwork the issue was fixed apparently, but if you encounter the problem just use this fix, it's not harmful or anything and even if web pages don't load you can still access the about:config just fine

@ShadyFennec hmm. firefox has seemed worse than usual for me lately, i'll keep an eye on how much CPU it's using

Sign in to participate in the conversation
Aleph

Generalistic Mastodon instance for open-minded people. Instance Mastodon généraliste pour personnes ouvertes d'esprit.