3 ms·
>and not suck memory like a vacuum cleaner. Not this again. It isn't 2003. If you want speed, then you want your browser to take up as much RAM as possible. Wh
by JonnieCache 15y ago
>and not suck memory like a vacuum cleaner.
Not this again. It isn't 2003. If you want speed, then you want your browser to take up as much RAM as possible. What else is it there for? Storing recipes?
Trust your kernel to manage your memory, it's cleverer and better qualified than you.
- shin_lao 15y agoFF consumes more memory than IE9 on my machine and is much slower. Consuming too much memory can slow down your program, especially if your memory gets fragmented. The kernel only manages the virtual memory, processes manage the heap themselves through an userland library (provided by the OS or a third party).
- JonnieCache 15y agoGood points. I probably spoke a little too hastily. I have become a bit aggressive about allegations of firefox's memory 'leaks' over the years, but I guess this is one place where people are actually informed enough to make them legitimately :)
- pnathan 15y agoNo, actually, I want my browser to take minimal CPU and minimal RAM. The browser is not the point of my computer use. Usually my editing and compilation is what my computer is for, and I hate every cycle that slows down my workflow. And, for what its worth, I clocked FF as breaking 500MB only a year or two ago, and I run under 10 tabs. Chrome does this better (or should), since it uses process-based tabs, which allow the kernel to manage memory, not the browser.