Firefox Enables Generational GC To Compete With Chrome
Phoronix: Firefox Enables Generational GC To Compete With Chrome
The latest Mozilla Firefox nightly builds have begun enabling the generational garbage collector to better compete with Google's Chrome on performance grounds...
Curious, but what addons/extensions are you using? Mozilla has often stated that some of its worst memory consumption/leak offenders were poorly coded add-ons. I'm sure some of the blame can be laid at Mozilla's feet, but it might not be all them.
Originally Posted by cb88
For reference, I've got 10 tabs open as well, and I'm sitting under 300MB memory usage currently. That's still more than I like, but it's nowhere near the 1GB you've got.
Currently enabled extensions:
Firebug (enabled but not active on any pages)
Garmin Communicator (to sync my watch's GPS recordings for biking/running)
I've got just over 300MB after hours of use, three tabs open, Adblock plus and Lastpass, plus Garmin Communicator, Flash and Google Talk plugins. Seems pretty damn reasonable to me.
Originally Posted by Veerappan
Now if they could only get Firefox for Android memory usage under control. It's often 2 to 3 times worse than Chrome's (on the beta, worse on stable).
FYI, the current GC in SpiderMonkey is an incremental GC using Mark and Sweep - it's equivalent to having a single generation. I'd expect that they are still using the incremental GC for each of the generational buckets in their new GC algorithm.
It really depends on the types of webpages. even simplistic webpages can kill your computer if they're of the infinite-scrolling variety. Google came up with a pretty cool concept of a paginated version of infinite scrolling. It's a shame they don't use it for G+ because that's the perfect demonstration of the drawbacks of infinite-scrolling pages.
Originally Posted by cb88
Adblock which netsurf also has builtin via css blocking... and DownloadHelper so one addon which "counts".
Disabled DownloadHelper... 260Mb after reloading the session. 600Mb after reloading all the tabs I expect it would jump back to 1Gb if I left it running for any length of time though. That said the other memory figures are still excessive even before reloading and such.
Eating lots of memory?
1) HTML/JS/CSS were designed with little more than humble web pages in mind.
2) JS requires 2-10 times more memory than C/C++, cause it's interpreted and cause it doesn't allow saving memory, like no types, any number is internally of type double (8 bytes) no matter what.
3) There's much back-n-forth stuff going behind the scenes, lots of images typically being scaled/cached.
The extensions/plugins do add up too.