|
|
|
|
|
|
by yellowapple
4145 days ago
|
|
|
I, at least, do typically run with anywhere from 50-200 tabs (or more!) at any given time. Yeah, there's some slowdown if you're running on an 8GB machine (I'm typing this on a Macbook Air with a Firefox session with at least 100 tabs open at the moment (SEE EDIT)), but it's certainly way more than I used to get with Chrome before I switched back to Firefox a couple years back (Tree View Tabs being the motivating factor). Currently using 5.4GB of RAM (OSX is reporting a "Compressed Mem" of 2.96GB), and it's currently pegging one of the cores of the i7 on this thing. This is after about a week of nonstop (i.e. same Firefox process) use, and with Flash present in a lot of places (like the 20+ Github tabs I have open, thanks to Github using Flash for its silly "click here to copy a link to your clipboard" feature; I really need to get those wretched things blocked); a lot of things will clear out pretty well after restarting and restoring the opened tabs (though this is partly because they're not loaded into memory again until they're accessed again). EDIT: After posting this comment, I closed all my tabs (something which causes one of my extensions - probably Tree Style Tab - to throw a confirmation dialog with the number of tabs). The number was 233, plus another ten or so in another window. I must say, that's pretty damn good, all things considered. I'm trying out Nightly right now to see if I can push that even further with the new e10s features. |
|
|
Now, I will admit that Firefox misbehaves once you hit about the 500 tab threshold (or higher) to the extent that closing it takes longer. But since tabs aren't loaded on restart until you click them, its memory usage tends to stay much, much lower during regular usage.
I want to like Chrome. It's fast, it's pretty speedy, but for my use case, it's not ideal. It's good for some things, but Firefox is much better behaved!