[OneWingedShark]

However, FF hasn't "leaked memory" in years. A TRUE memory leak is one where RAM is consistently lost to the process until the process either locks up or the system crashes.

It happens, really.
Try running it continuously for about a week with, say, 50 tabs open.

FF is a safer, more stable browser than IE and while it's not as streamlined as Chrome, it's much better at error handling.

I kinda don't care.
I don't want to measure crap with other crap (relative stability), I want solid, absolute stability like that which formal methods can deliver (i.e. provably bug-free).

Remember that Mozilla is a standard-bearer for much of the open source community. They're not a for profit entity, so their value isn't really at issue here, I believe.

I agree about the money /= value for the organization; however, being as it is standard-bearer for open-source they ought to consider using formal methods rather than infinite-updates as their tool for ensuring quality.

[rarestia]

50 TABS?! That’s incredible. I’ve never seen that many tabs open in my entire career as an IT engineer. I’m surprised it would run for more than 5 minutes let alone a week. My FF stays open between sleep (STR) sessions for 5 days and rarely eats up more than 400 MB.

If you want stable, try running any browser in “Privacy” mode where all add ons, browser plugins, etc. are disabled. It’s incredibly stable, regardless of browser, but it lacks function. Worst case, you could always go back to Lynx or Emacs.

[Resettozero]

Try running it continuously for about a week with, say, 50 tabs open.

No thanks. What on earth are you DOING with so very many tabs open? Unless you're deliberately trying to freeze it.