I use Firefox daily as my default, have roughly about 250 tabs open at this stage. I've not closed my browser in the last 6 or 7 months.. It's not crashed yet.
Is it possible that it's some specific website your visiting?
One is that I use Bluetooth headphones, and with my coming and going sometimes something gets into some weird state. Youtube freezes, and sometimes Firefox locks up and crashes as well. This is probably Pipewire's/Fedora's fault primarily, but Firefox gets caught in it.
I also notice that a network drive getting stuck gets Firefox killed. Like if a NFS drive (which I'm not using right now, mind you) just isn't mounting because the VM that provides is down, and I open a file dialog, Firefox will get stuck then get killed after a few seconds.
I guess you could say that neither is exactly Firefox's fault, but I'd say it needs better error handling.
I’ve not seen a single application yet, which handles audio system failures properly when it happens during runtime, and most of them fails even when it happens before starting them. And it’s quite frequent unfortunately with my gazillion different Bluetooth and wired headsets across multiple laptops. It’s definitely not Firefox specific. It’s basically standard.
There's probably something to blame in pipewire/fedora's configuration.
I know that at least Pulseaudio has a "null" output driver, so if the audio hardware suddenly disappears, at least under PA it's possible to have applications happily deliver audio into the void without noticing a thing, and then switch back to hardware when it comes back.
I'm not sure if Pipewire deals with this worse or just isn't configured right.
Had to install an auto-reload extension to reload the Slack page every 15min, as it would live-leak some js or DOM stuff causing Firefox to run out of memory eventually (ie 10s of GB).
Haven't checked recently if it's been fixed, I just leave it on.
One is that I use Bluetooth headphones, and with my coming and going sometimes something gets into some weird state. Youtube freezes, and sometimes Firefox locks up and crashes as well. This is probably Pipewire's/Fedora's fault primarily, but Firefox gets caught in it.
I also notice that a network drive getting stuck gets Firefox killed. Like if a NFS drive (which I'm not using right now, mind you) just isn't mounting because the VM that provides is down, and I open a file dialog, Firefox will get stuck then get killed after a few seconds.
I guess you could say that neither is exactly Firefox's fault, but I'd say it needs better error handling.