Firefox fixes save gigabytes of memory on image-heavy pages

Re:Firefox fixes save gigabytes of memory on image-heavy pages by velodrome on Tuesday October 01, 2013 @07:25PM (#6479742)

I agree. Chrome has NEVER been lightweight in terms of memory. Each tab is in its own sandbox environment. It will need to load resources separately for each sandbox and that chews up memory.

Chrome may be inefficient with memory but I could manage this by closing the tab. Firefox would retain the memory even after the tab has been closed for some time.

Firefox is a lot better these days.

[ Parent | on HN ]

Re:Firefox fixes save gigabytes of memory on image-heavy pages by celeryreally on Tuesday October 01, 2013 @08:36PM (#6479947)

That seem's to be the desirable outcome, if the trade-off for perceived speed is a larger memory footprint. Users directly feel the speed, but are less likely to be affected by a larger memory footprint.

[ Parent | on HN ]

Re:Firefox fixes save gigabytes of memory on image-heavy pages by halviti on Wednesday October 02, 2013 @07:33AM (#6481816)

Just closing the tab isn't enough to release that memory though.

Lets say you have 200 tabs open, check your computers memory usage, close all of the tabs but one and see how much your memory usage drops. Then close that last tab (or fully quit the program on a mac), and see how much memory you get back.

I typically get about 1/4-1/2 of my total RAM back after closing the program entirely.

[ Parent | on HN ]