Originally posted by: Tegeril
I've never seen any of the Firefox issues that were reported above and I leave it running for days, it's never allocated more than 50mb of virtual memory in those time periods, never crashes, and responds quickly always. You've got some other issues.
I did note that my experiences were in corner-cases, involving worst-case behavior on low-memory (aka run-of-the-mill, as opposed to most "power-user") systems.
I will add a foornote, after installing an additional 2 x 256MB DIMMs, bringing my total RAM in this system to 768MB, that after having Firefox running for nearly a week now, that it hasn't crashed, seems fairly responsive still, but right now, it is using 514MB of virtual memory all to itself.
As long as it's VM footprint remains mostly in RAM, the worst-case behavior stemming from the broken GC handler behavior, touching most of the dynamically-allocated VM data multiple times per page operation will not be noticable. It's only when the VM size exceeds RAM and starts thrashing, that the application (and UI, because the UI is rendered via the browser engine) latency becomes all-too-painfully apparent.
Somewhere I bookmarked a list of the nearly 30 or so odd bugs related to all of this mess.
The Moz dev group has been doing marvelous work on Firefox, I must admit. But it still shares the "broken" core code of Moz, and these issues still affect it. I can attest to that running the same nightly 0.8 build that I am currently running, only a few weeks back when I only had 256MB of RAM, having to wait several minutes after closing each tab, before the browser would respond again.
Moral of the story? Mozilla/Firefox, is NOT for systems with less than 512MB (or more) of RAM, unless browsing is limited to short sessions, closing the browser completely after every session. Opera, OTOH, runs fine, with far less VM bloat and bad VM behavior, except of course for the security and other crashing bugs, which are IMHO enough to avoid using it still. (But when is Moz going to get crash-recovery features? There have been outstanding bugs on that issue for *four* years.)