Same, been using it for over 20 years and probably only a handful of crashes in that time. But I mostly look at dead simple web stuff (like hn) and run aggressive ad blocking so I might not be representative of the average user
Its pretty stable for me, except it has some memory leaks. Generally I gotta leave heavy pages open for days at a time to notice, but if I don't close it entirely for over a week or two it will start to chug and crash.
It really depends on what you're doing with your hardware. Overclocking, overheating, unstable power supply, and things like that increase the likelihood of memory bitflips.
Slack caused frequent FF crashes, until I realized Slack has (had?) a live leak. Added an extension which force-reloads the Slack page every 15 minutes and that stopped the crashing.
I can also go months and don't see crashes (though occasionally I'll hit a memory leak where closing tabs doesn't release it so I'll restart firefox then), but unless ThinkPads come with ECC I don't have it.
I run Gentoo, and compile FF from source. I don't think the Gentoo repos update the FF version that frequently. And even if they do and I compile the latest one, I don't automatically quit the existing running version.
Same, been using it for over 20 years and probably only a handful of crashes in that time. But I mostly look at dead simple web stuff (like hn) and run aggressive ad blocking so I might not be representative of the average user
I run FF on Mac laptop, Windows/Linux laptop, and Windows desktop and can’t remember it crashing in years.
Naively, the more stable a piece of software is, the more likely that its failures can be attributed to hardware error.
Its pretty stable for me, except it has some memory leaks. Generally I gotta leave heavy pages open for days at a time to notice, but if I don't close it entirely for over a week or two it will start to chug and crash.
It really depends on what you're doing with your hardware. Overclocking, overheating, unstable power supply, and things like that increase the likelihood of memory bitflips.
Slack caused frequent FF crashes, until I realized Slack has (had?) a live leak. Added an extension which force-reloads the Slack page every 15 minutes and that stopped the crashing.
The only browser I’ve crashed in the last decade is mobile safari, and that’s probably because it runs out of memory
Months in my case. But I have ECC. Every five years I build a new development workstation and I always have ECC.
I can also go months and don't see crashes (though occasionally I'll hit a memory leak where closing tabs doesn't release it so I'll restart firefox then), but unless ThinkPads come with ECC I don't have it.
Does "Weeks on end" = 4? Or do you not take the latest update every 4 weeks?
I run Gentoo, and compile FF from source. I don't think the Gentoo repos update the FF version that frequently. And even if they do and I compile the latest one, I don't automatically quit the existing running version.
That's easy to ignore.
How many DRM-heavy websites do you use? Widevine is a buggy thing.
macOS crashes more than Firefox for me.
Yes