101–110 of 410 posts
What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]
Not working for me.
Reddit Thread with tons of comments already: https://old.reddit.com/r/firefox/comments/s2u7eg/is_firefox_... I have the same issue, a different profile worked edit: Twitter feed https://twitter.com/search?q=firefox&src=typed_query&f=live There better be some hell of a post mortem edit2: `network.http.http3.enabled` in about:config to false fixed it for me. Source: https://old.reddit.com/r/firefox/comments/s2u7eg/is_f…
This didn't fix it for me until I also disabled DNS over HTTPS.
It seems another workaround is disabling the collection of usage data: 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.
What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]
It is time for Mozilla to stop messing around. They are losing user trust extremely fast. A silent FireFox update that cripples the browser? No active update was done since yesterday and this morning: a broken browser. Please stop non-browser development and let me pay a monthly fee for a decent browser! I don’t want a VPN service, bookmark readers or other crap. I want Mozilla to defend the open web and create an op…
I don't understand the anger about the VPN. I think it's a good idea. Reader mode is useful, especially if you block a lot of CSS and JavaScript by default with uMatrix. I don't know why people use DOH anyway. It bypasses your hosts file, so you can't block things as easily.
Weird data point. Firefox on my laptop borked as per this thread all of a sudden. I spent like 30 min trying to troubleshoot it and failed, then i moved to my desktop and there it was, working Firefox. I'm posting this from it. Have they already fixed the problem and it was remote?
EDIT: FIX worked temporarily.. had to go the network.http.http3.enabled route, sorry folks I literally just fixed this problem by installing that microsoft visual redistributable https://support.mozilla.org/en-US/questions/1326304 It just started happening to me after i updated firefox.. I installe that VC runtime, restarded, and now it works.. didn't have to disable anything in the browser.. this has been happening…
Last time Firefox wouldn't connect to stuff (Google sites) even though every other browser would (March 21~22, 2017, but I think that was a problem that didn't affect the whole world), the workaround was very similar to the one discussed in other comments here: disable network.http.spdy.enabled and network.http.spdy.enabled.http2
(Insert snarky comment about feature creep and questionable frontend engineering here)
Earlier quoted context omitted.
It seems like it has nothing to do with the version, so it's not an update from Mozilla's end. Still bad though.
If that's the case then I might be wrong. But I remember updating somewhere yesterday and using FF for a couple of hours before stopping for the day. This morning no pages loaded anymore. Hope I didn't jump to conclusions, but still.