mozilla firefox browser keeps crashing in youtube

And not until you were hammered with facts after facts and reason after reason did you submit that you didn’t really know what you were talking about. But it didn’t matter, you dug your heels in anyway, even when this much was pointed out. You didn’t have the requisite knowledge to come to the conclusion that you were pushing. Even though you had been provided the facts, you had the attention of the frontline devs, you had people actively working on the issue AND providing updates on their efforts, you still felt a need to dismiss all that and end up with a discouraging assessment of their work. Instead, you came with your highly offensive and inaccurate assessment - “…it has been so unstable lately”. But none of that seemed to be good enough for you. But they went to work anyway to try and work around the issue while the Mozilla team works on providing a definitive fix. They even advised that this was something triggered by Firefox. You raised an issue, the responsible parties immediately went to work. Starting the post is not the problem, making a firm assertion that’s baseless and unsupported by facts is. However, this isn’t about me, but since you want to make it personal, I’ll indulge you… Am I passionate about Jitsi and the developers? Heck, yeah! And I believe everyone who’s been a beneficiary of their generosity should be too.

Just my Considering the blessing that Jitsi has been to me (and to others), I think it would be remiss of me not to speak up when there’s a mischaracterization of the project - or the efforts of those directly behind the project. The team does an incredible job (I know you agree with this) and the least we can do is to encourage their efforts (yes, this includes providing useful feedback, even if it’s about negative observations - but it should be done without assertive assumptions). Your earlier assertions that Jitsi ‘breaks things’ is disturbing (I actually want to say “offensive”) and the fact that even with initial explanations, you chose to dig in made me wonder if you were just choosing willful ignorance (again I don’t like to judge people’s stance as this) over explained facts.Īnyway, hope the information shared gives you better context. It is certainly understandable that we all may not be quite as knowledgable about certain things in certain domains, but what I find a bit unsettling is when someone speaks authoritatively and with certainty about something they’re in fact uncertain or unknowledgeable about. I don’t like to term people’s views as “ignorant” and I’m even less inclined to label someone as “stupid”. It seems hardly reasonable to expect people who come to the users forum to know the inside baseball of what’s going on with browsers. In this case, let’s please refer to it as “ignorance” instead of stupidity. It would be nice if that cutoff of support was well-defined and documented though. You have to have some cutoff of support, otherwise you end up spending all your time on accrued technical debt. No project could possibly maintain workarounds for all of those in perpetuity - the codebase would become completely unmaintainable. Every browser release has different quirks/bugs, especially with WebRTC.

Jitsi Meet used to be the one video conferencing system that worked no matter what browser you had. On the other hand, although I haven’t seen a published policy about how long old browser versions are supported for, given the tiny share Chromium 90 has, it wouldn’t surprise me if maintaining support for it was a very low priority. If the bug is reported, easy to reproduce, and can be fixed without any impact on more widely used browser versions, it might well be fixed. That’s also fair, and it is good for me to know to not waste my time or yours hunting down bugs for extended support browsers. I guess I’ll take that to mean that whatever change was made three weeks ago that makes the older versions of Chrome/ium crash immediately is never going to be fixed.

Mozilla firefox browser keeps crashing in youtube