2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]Another score for automatic updates I guess.
The other thing I noticed was that previously when I looked in taskmgr (windows 10) there were 4 or 5 firefox processes going on -but when I went to close firefox after setting that to false there were not.
I'll close and check again but I'm wondering if simply setting it to false once doesn't allow it to perform some update or something that lets it get back to behaving normally? Like unsticking a log jam?
[edit]Forget I said anything. When I restarted and tried to reload HN it hung again. I had to disable network.http.http3.enabled in order come back and edit this comment.
EDIT: my FF version is 91.5.0esr (64-bit) on MacOS.
Many of my colleagues had the same issue today, and they all report that just restarting FF fixes the problem (one restarted the computer itself).
Thank you.
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 open source browser. That’s it. The past few years have been a big disappointment in Mozilla leadership and (lack off) vision.
If they don't turn this around then I hope others will step up and reclaim the web!
This isn't just a rant, it's also a cry to let people explicitly support browser-only development via donations, subscriptions and show our support.
What's going on at Mozilla is probably what's going to happen for Linux once Linus is out.
Both these pieces of open source software are way too big to be replicated now by a dude or a bunch of dudes and also way too big to be maintained by people on their free time. They require resources and organization which itself corrupt the original spirit.
Or maybe that whole firefox debacle made me a little gloomy today...
Since we are sharing our impressions, mine is that the Mozilla Foundation's current CEO doesn't believe in Firefox. Instead, I think, they are leveraging Firefox' popularity to try and position the Mozilla Foundation as a defender of internet freedom, at which point they won't need Firefox anymore.
What happens to Firefox once they achieve that? No idea. The cynic in me believes they will keep doing whatever Chrome is doing until the project is virtually dead, but I honestly hope I'm wrong.
... from whom they get the money. Its primarily Google who keeps Firefox alive to prevent lawsuits against their market dominance due to missing alternatives.
A clear indication that they are in that area a de-facto a monopoly.
> Both these pieces of open source software are way too big to be replicated now by a dude or a bunch of dudes and also way too big to be maintained by people on their free time. They require resources and organization which itself corrupt the original spirit.
I doubt that one. There are a lot of big companies who employ the core developers as well as the Linux Foundation which employs Greg K-H [1]. Unlike Firefox where there isn't much corporate interest behind it, there is an absurd amount of corporate interest behind Linux so in the worst case the Kernel will become a corporate committee joint effort, but definitely it won't go down the hell that Firefox currently is.
I don't know why people use DOH anyway. It bypasses your hosts file, so you can't block things as easily.
Pretty sure they meant Pocket when referring to a “bookmark reader”.
It doesn't bypass my hosts file... I have a couple of locally hosted websites that I have rules in /etc/hosts for, and Firefox resolves them correctly even with DOH enabled.
To make it slightly less visible what websites do you visit.
To bypass DNS-based censoring some ISPs deploy as some governments require them.
The 'open web' died when Chrome overtook Firefox and are still paying for more than >85% of all their revenues just to be on life support in return for ruining the 'open web'.
> If they don't turn this around then I hope others will step up and reclaim the web!
The web has been reclaimed by Google from Microsoft - exchanging from one behemoth to another. Firefox is always behind Chrome's features and many web developers still continue to place banners on users to 'Switch to Chrome'. So it is already over before it has started.
> it's also a cry to let people explicitly support browser-only development via donations, subscriptions and show our support.
One more thing, even if one was to support via 'donations', they are not funding Firefox, it is funding something totally irrelevant in Mozilla and Google is once again keeping them on life support.
What a magnificent disaster.
Have you any idea how complex a browser needs to be? I hope this team of plucky, idealistic coders can keep up with all the latest and greatest web developments devised by the thousands of engineers at Google et al.
The web as an open, human-sized system is dead.
I think a decent layout or CSS library would be useful outside of a web browser, too.
Then I would also only focus on the subset of websites that are "documents", not "apps". If I could decide, HTML6 would have two profiles: one ultra restricted (maybe no legacy stuff and no cross site scripting) for "documents", and one where you can do all kinds of crazy stuff like "web USB" for "apps". That's not going to happen because Google and Apple like the "open" web as complex and messy as it is, because it gives them total control as you know. But it doesn't stop a browser vendor from building a browser with two engines - your own engine for the majority of documents and chromium for webapps.
Unless you are a billionaire, you can't afford to. Developing a decent browser takes enormous amounts of money, good luck funding that of voluntary donations or monthly fees if in most technical aspects superior free alternatives exist. Firefox is failing badly on a few hundred millions a year; I'm sure you could do better with a CEO who isn't just a parasitical non-entity, but I doubt better enough to make that idea viable.
> This isn't just a rant, it's also a cry to let people explicitly support browser-only development via donations, subscriptions and show our support.
A pipe dream -- the web is a dead end. If you want something that can live off donation support (as opposed to selling off its users as cattle), you need a new set of protocols. The whole web stack is such a clusterfuck of layers upon layers of crap with one dominant player who can always add more of it when it suits them to slow down competitors (including bugs you need to replicate for compatibility purposes) that there is not the slightest chance of some grassroots alternative emerging.
What would be the model to get started? Can we start by funding a fork (similar to iceweasel) with the eventual goal of hard forking once the needed resources are available?
I like you would be more than happy to pay $10/month. I pay $20/month for a bike! (relatively cheap in Denmark where taking my good bike to the shop costs me ~$500 every time I fall off). The problem is that there isn't a box on the internet for my CC.
Fortunately, you're just one person voicing your opinion in an unrelated corner of the Internet and you seem to be in the minority otherwise Mozilla would have made the changes you want already. Most other people either find those features useful or are indifferent about them. I, personally have no qualms with Mozilla doing what they do even if I might not use those features.
If you really want change, start contributing and bring it about yourself.
However I do recall Mozilla having another backdoor channel which they used sometime ago to push an emergency update. I hope that works.
Can't access any website or making any connection without disable `network.http.http3.enabled` and restart.
This impact is huge for million of firefox users!
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.
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.
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.
Windows 11 almost but not entirely broke HDR. It kinda-sorta works for some things, sometimes, but most apps that used to work with HDR back in Windows 10 just can't any more and are forced to use SDR with sRGB gamut only.[1]
The Win UI SDK regressed from WPF and lost all wide-gamut or HDR support at the API level (which probably explains the above). As in, Microsoft literally removed a wide swath of floating-point color support along with the wide-gamut scRGB color space. We're back to 8-bit RGB arrays in sRGB only as the only option. Like in the 1990s.
Windows Server 2022 can't activate its license unless it uses the UTC time zone. Why? Because Microsoft employees test using Azure VMs, which... use UTC by default.
Speaking of color: Firefox for a while just... stopped doing color management. Then it worked again after a few weeks when it updated.
But it might not be Firefox's fault, because Windows also seems to randomly turn color management off, or force it back to sRGB silently.
If you have a laptop with one of those hybrid Intel+NVIDIA GPU combinations, then HDR games don't work at all with the built-in display, they all report HDR support as N/A. But they will work with external displays!
Speaking of HTTP/3 in Firefox: I've had it permanently disabled because the early releases would leak about 10 GB of memory per minute and lock up the browser very quickly. But not quickly enough to prevent the automated test suites from passing.
... and so on...
The point I'm trying to get to is that in 2022 we've achieved this state of affairs where human beings don't do actual Quality Assurance any more as a job. It's all automated and those people have been summarily fired.
Any issue that is invisible to a DevOps pipeline is Not A Bug and will ship broken. If it ships in a working state, that's probably just a lucky accident, and a subsequent patch will break it for sure.
All of the issues above are caused by automated test suites one way or another. Automated tests are literally blind to output color rendering; testing that requires a physical monitor. Automated tests are almost never set up for long-term testing for things like memory leaks, because they have to run fast. Automated tests use default, vanilla settings for the host OS. Automated tests don't have funky hardware combinations. Automated tests don't measure "jank", or inconsistent performance issues, Etc, etc...
What you're experiencing is the end result of all of this. NOBODY is sitting down and validating the end-result from the perspective of a human user sitting in front of an actual device. That final quality assurance is just not there any more, and hence we're all embarrassed when we have to "show off" some piece of IT tech and find that it's just a broken mess.
/rant
[1] This bug has apparently been fixed in some beta, and might ship around the middle of this year. In other words, Microsoft is perfectly content to break display output on their consumer desktop operating system for six months and just leave it at that.
Earlier it said the other AV solution was turned off (it was not) and I had no valid protection.
Now it doesn't even say an excuse. It just keeps running with no obvious way to turn it off.
Surely it was good UX to remove that "clutter"?
Want it better? Augment competition and try to avoid monopolies.
EDIT: Actionable advice: avoid SW or HW which isn't at least 6 months old.
We are only valued community members when there is a fundraising drive going on. The rest of the year we are just annoying nobodies it seems.
Try to ask for updates on the Tab bar issue if you want to trigger it again.
I mean, in normal circumstances I'd understand it, but hiding this kind of key information as "advocacy" is unacceptable.
So data snooping is the issue here.
So I have to open Safari and download and install the latest release.
Which means I can never count on Firefox working. Frustrating.
osx, if that helps anyone suggest a fix.
But I'm starting to believe that the browser wars have been conclusively lost and it's time to throw in the towel. Losing a whole morning on this trick is really pissing me off, I'm in the middle of a bunch of stuff and if not for this HN thread I'd be unable to continue to work. Very, very annoying. Browsers are mission critical, you don't just fuck around with the networking settings on a timed change.
> Browsers are mission critical, you don't just fuck around with the networking settings on a timed change.
Is that what they did? I thought the problem was a server-side change by a Mozilla vendor. And if they did, how else does Firefox update networking? How does Google do it with Chrome?
Can you imagine if this situation happened to someone in the middle of the exam? I'd never blame the browser for a loss of connection before a good few minutes of trying everything else.
Also, an update (auto or manual) means restarting the browser, which logs me out of my sessions, profile, and password manager.
I was and still am an evangelist but stuff like this makes me wonder.
Never saw a bug like this in a browser. By pure chance did I check if Chrome worked.
In contrast to all the heat from many of the comments here, I'll say this: shit happens to any company. My trust in Mozilla is not (yet) shaken just because a bug made it into production, even if that bug made it there due to bad decisions or even (hopefully temporary) lack of vision.
I, for one, am not comfortable with giving full control of the internet to Google and friends, so using FF is one of the things that let me "fight".
Why? Whatever you install is likely to have issues with similar impact.
Update: using Google's (the horror) DoH, and I didn't notice problems. Might just be CF having a bad H3 deployment, but I want to know what bug it triggered on FF.
Update 2: To clarify, CF did indeed hang FF, but also Google, which is know for at least bothering to monitor complaints (and dns.google is still H2). Trying to disable telemetry now.
Update 3: incoming.telemetry.mozilla.org is still H2. Can someone give me the other domains of MozTelemetry? Browser still working as of the moment.
Update 4: Telemetry was indeed H3'd: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17, me angery right now.
It sounds like users with telemetry disabled were not affected.
EDIT: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c19 this is seemingly not the case, other HTTP/3 services can also trigger the same bug, telemetry just happens to be the most common / first to be triggered
I've had it working intermittently all morning but after that setting got set to false it never failed.
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 for at least a year, reading reddit and googling..
audit: type=1400 audit(1642063521.864:246): apparmor="DENIED" operation="ptrace" profile="snap.firefox.firefox" pid=9868 comm="Shutdow~minator" requested_mask="trace" denied_mask="trace" peer="snap.firefox.firefox"
I really don't like it, but turning off Apparmor worked for me. Not sure what caused AppArmor to start complaining all of a sudden.
There are apparmor profiles for Firefox, e.g. this one: https://github.com/nibags/apparmor-profiles/blob/master/appa... Maybe you could add it to your system and see if that fixes things.
Thanks!
It's only my laziness (having to recreate all the setup, find equivalent extensions etc.) that keeps me from switching to another browser.
Crashing tabs, losing pinned tabs, having to restart the browser when I switch to another wi-fi (eg. return home from the office), or otherwise all I'm getting is SEC_ERROR_BAD_SIGNATURE errors (not a problem for any other browser somehow!)... or even those silly dialogs that inform me "Firefox is already running, just not responding" when I close and try to reopen it, because apparently it lingers in memory, sometimes for like half a minute, when I'm only trying to get stuff done. These little slaps in the face really add up over time.
And even if they do, can you trust google that they're not watching everything you browse through a mechanism that privacy extensions cannot affect? For example the malware database.
> 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.
Couldn’t they have used any other cloud provider? I mean, cmon!
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_firefox_...
If anything, I think there's been regress. There was a time, long past, when I didn't really have to think about the browser itself much at all. It just did its job and problems were rare. Browsers and the web have turned enormously complex now. WebGL is a case in point: it's complex by itself, and it also brings in all the complexity of the graphics drivers & GL implementation on your system. Graphics drivers are the most complex of all drivers on your system, and GPUs are the least reliable of your components..
Other workaround: Go to preferences -> Firefox Data Collection and uncheck everything. Then restart Firefox[0]
[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c6EDIT: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c21 yes, it's not just telemetry
Feels like Firefox waits some amount of time before making fresh attempts to a previously failed site, possibly due to some caching.
I've only spoken with 2 other people and they were not as lucky as me to have read about the fix on this very comment page, so they were "forced" to use Chrome/ium to be able to access the web. Not sure they will switch back to Firefox.
I am surely not switching to Chromium based browsers, but it is time again for me to consider switching to Icecat or so instead after what happened today.
If that's true, it's good news for Firefox. If that's all it takes to lose 0.05% of users, then when Chrome has a bug and loses 0.05% of users to Firefox, there will be a large net gain.
At this point a developed a love/hate relationship with Firefox.
It’s the only browser I use, but you need to be delusional to not see that you’re in a sinking ship and everyday you find a new hole and you see more water coming in.
"HTTP/3 uses QUIC, a transport layer network protocol which uses user space congestion control over the User Datagram Protocol (UDP)."
Ok. Is it still a thing with internet core routers that in case of congestion issues they drop datagram packets because they're not guaranteed to be delivered anyway?
Manually reverted, and launching my older version (92!) demanded I either create a new profile or quit.
This would have been a disaster except I tried it out on a spare profile in the first place, so I recommend this to anyone making a similar experiment.
I haven't set DOH (!) that I can remember.
Running through the initial ff setup a couple of times is a sad reminder of the progressive influx of crapware into my sill favourite browser.
Have they already fixed the problem and it was remote?
Or you simply didn't know that Firefox made it the default a while ago. I had it intentionally disabled on one machine but forgot that it's enabled on others, which made troubleshooting even more "interesting"... Why do things work on one machine but not the other?
Oh, interesting! I did not know it is a default now. I can imagine why they would enable it by default, but when Cloudflare (which I assume is the default DoH provider) has a problem at some point everyone is doomed.
Really wish they also could make it so the data collection part is opt-in instead of opt-out (which at this point in time appears to be the actual cause of this problem).
I really try hard to like Firefox but it keeps falling behind. For certain tasks like debugging web applications I already resort to Chrome because the debug tools in Firefox are painfully slow in comparison. I guess FF developers have too beefy laptops and don't notice this, on my "old" T460p it makes the browser more and more unusable though. Same goes for opening "expensive" web apps like Slack or video conferencing tools, performance greatly degrades.
Thanks, I wondered what was causing that.
Edit: I am on Firefox 91.4.1esr, so clearly it isn't just the latest versions that are affected.
Twitter[1] is currently lighting up with broken FF reports across the globe.
Some people are reporting that if you hold down Shift while opening it works (though any FF personalisation is wiped). That didn't work for me on Mac.
[1]: https://twitter.com/search?f=live&q=firefox%20until%3A2022-0...
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)
Seems like I'm disabling automatic updates for the foreseeable future.
You might as well use Brave. Which that is a good choice.
This whole incident makes me feel better about myself. Like any developer, I’ve deployed some nasty bugs into production. But I’ve never completely broken a web browser relied on by millions. My heart goes out to the FF team members working to fix this.
I was in the middle of a chess game. I played a move and the opponent's clock just seemed to be ticking down. The correct response for them was obvious so I couldn't understand why they were taking so long. Eventually I became suspicious and realised all my firefox tabs were kind of "stuck" and I couldn't refresh anything etc. Eventually my opponents clock seemed to run out completely but the game didn't end. I had to forcefully restart my firefox and when I got back to my game (fully expecting to have lost on time) saw that my opponent had played a terrible blunder and immediately resigned.
The fault occurred mid-session, whilst streaming a live broadcast, and I lost the connection.
Plenty of people using the opportunity to criticise Mozilla, but if it's a third-party srvice problem, you can't blame them.
I would like to come back to Firefox. But lack of focus on their core product (vertical tabs issue) and trying to woo chrome(ish) users with crappy products have turned me away long back.
That's pretty poor on the mods :(
I opened JetBrains Rider (on Fedora 35) and debugged my site (Alt + F5) and it launched to a blank page with FF locked up.
So this isn't to do with ME specificially trying to connect to an external service.
No need to change any settings.
The strange thing it seems to randomly appear/disappear.
Most strangely it happened to trigger the appearance/disappearance of the problem with other people entering the office??
Edit: confirmed this on two separate machines where Firefox was unresponsive (Win 10 and Ubuntu 20.04)
(Closer examination of default-deny firewall shows that HTTP3 are being blocked due to custom UDP connection tracking.)
I’m fine with that.
Tested all versions, release, dev and nightly.
They all work now.
I did not have to change any settings or do any fix.
I "fixed" it by refreshing Firefox. You can refresh Firefox from [Help] menu item, and choose [Trouble shooting Mode...]
I rebooted my PC and it seems fixed. Weird how this bug suddenly pops up. I don't even use DOH. I had to kill the process on Linux to even restart Firefox, but I needed a full reboot to get connections again.
Bring on the front lines for such a crucial and complex piece of software and associated infrastructure is tough.
Edit: And it broke again after working for 15min. Fairly strange.
Edit: the issue came back after reinstall! I had to disable http3 in about:config to resolve this issue.
Menu > Help > Troubleshooting Mode (it asked me if I wanted to refresh)
- lets us opt of automatic meddling from Mozillas side
- fixes a single small thing every month
I want to pay for it.
I thought my internet was down but nope, it was Firefox. Everything else was working fine.
"Allow Firefox to send technical and interaction data to Mozilla"
At this point it is pretty obvious.. they don't even try anymore, what a shame this place has become