It's obvious that most of those random crashes are caused by memory starvation. They should have all the telemetry they need to understand and fix it, if only by popping up an error message saying 'Not enough memory to render this page' or even Safari's maddening version of the same message ('A problem occurred with this web page so it was reloaded.')

The only explanation is that they don't give a crap. Very frustrating.

Reading the bug thread cited above, it may even be a case of, "I was able to get Chrome to crash under similar circumstances, therefore it is conforming behavior. WONTFIX."

Back when I did use FF, anytime I actually tried to report bugs I would just get the canned response, "disable your plugins and reset your user profile".

> Not to mention the weird random full-blown crashes that occur when I try to use it that I can't reproduce, no point in opening an issue for those

What platform are you using? I have used FF exclusively for 10+ years on Linux. Ubuntu and OpenSUSE every day. Nouveau and i915 every day. If I said I get 3 crashes per year in the last 3-5 years that would probably be exaggerating.

True for me as well, similar setup (amdgpu, not nouveau, except at work).

The only time FF 'crashes' is when I update while it's running, and even then it gracefully degrades and lets me know I have to restart it. With the 'restore previous session' menu option (an option that only exists in piecemeal and implemented much worse in Chrome), this is a mild inconvenience.

Chromium crashes much more frequently for me on Linux.

Exclusively Linux. I have used both Intel integrated and AMD graphics. No clue what's causing them.