I think something is wrong on your system.
That said I still use and prefer Firefox, but I also have to open up Chrome probably once every few weeks for various reasons, and it has occasional abhorrent behavior that I don't experience with any other program on the same machine.
For me what did it was switching to wayland (sway[1] specifically, from dwm on x11). Now it's a good step faster than chromium.
I agree with the sibling comment; there's something wrong going on, what you're describing isn't firefox's baseline.
[1]: https://swaywm.org/
https://wiki.archlinux.org/index.php/Chromium/Tips_and_trick...
It would however help a lot if you wrote in a style that made it clear that this was your personal experience.
I'm using an Ubuntu based distro myself (KDE Neon) and have no problems.
I downvoted the comment. I'm just not sure it adds anything useful to the conversation when it's not representative of the vast, vast majority of experiences that users have. It sounds like an anecdotal, isolated issue. I didn't post a top-level comment to say I've been using Firefox for over a decade without it crashing because it's just not remarkable or interesting.
I'd be more interested if some crash reports or BugZilla issues had been linked to substantiate the comment.
For what it's worth, I'd have downvoted a comment made in the same vein regarding Chrome too.
Edit: Here's the related bugzilla report
Is it intentional? It sounds like the distro's package manager is swapping out the binaries from underneath it whilst it's running. I have some sympathy for the devs here, because I suspect it doesn't happen with the built-in updater (which, let's face it, most users will be using) which probably swaps the binaries on next start-up and just invites the user to restart the browser.
Chromium invites the user to restart. Firefox redirects every request to about:restartrequired