They're already fixing memory leaks. In fact, Firefox now uses less memory than Chrome.
Let me guess, you're another person who hasn't used Firefox in a few years hasn't bothered to check out the latest versions at all? :)
Let me guess, you're another person who hasn't used Firefox in a few years hasn't bothered to check out the latest versions at all? :)
And yes, I am using the latest build, I check about:memory regularly, stripped out the unneeded add-ons, but maybe I've just got too much stuff open and those pages have lots of script activity.
Is my usage the issue or is there something that can be improved in my scenario?
There can be a very drastic difference between "virtual memory made visible to a process" and "physical memory actually used by a process", especially in the context of shared memory systems where you have 5+ processes that are able to share much of their text and data segments.
I don't have Firefox here so I forget, but does their about:memory page show the "proportional" memory usage? KDE's KSysGuard has a detailed memory usage calculator that can display stats like that.
While I feel Mozilla has tried to address the memory leaks, I still think there is a lot of memory bloat for my usage.
What extensions do you have? I've also disable Java, Shockwave, etc. Try Nightly? I've never had a single stability issue.
Other people mentioned the about:memory tab. Taking a look at it now, I'm seeing about 80-100MB difference between what that tab say and what the activity monitor says.
That said, the developer tools (both Firebug and the newer native ones) are really just not on par with Chrome now. I know they have people working on it, so I am looking forward to what they come up with.