Re:Firefox fixes save gigabytes of memory on image-heavy pages
by gamache on Tuesday October 01, 2013 @04:55PM
(#6479039)
I'd also like being able to open that many tabs and have my browser perhaps release some of that memory and just reclaim it when I open the tab for reading again.
Chromebooks do a great job of this -- inactive tabs are often freed when memory is needed elsewhere, and reloaded as necessary. I wonder if that feature is going to come to Chrome outside of ChromeOS.
Re:Firefox fixes save gigabytes of memory on image-heavy pages
by jordanthoms on Tuesday October 01, 2013 @05:25PM
(#6479179)
That's also done on Chrome for Android.
Docker is real nice, although I might go for pure LXC the nex time I build something. But I'm developing on OSX (as many of us, I believe). So _not_ running a VM is not really possible here. I deploy on Linux, and like to have my environment very consistent, hence the VM. Granted, with Docker/LXC I could probably get by with just one VM and a lot of little apps running side-by-side, but that's not how my current setup and projects work, yet.
At any rate, less memory used by browser is more memory for me, to use any way I want.
I already love the firefox behaviour that when it restores your tabs, it doesn't actually load them until you click on them. Awesome startup speed improvement.