I'm really curious about this as once I get to about 10 tabs my brain starts wanting to close them to get back to something it can manage. This is either because I'm dumb (highly likely) or because you have a different usage style than I (also likely).
So if you don't mind elaborating, how do you get to where you have that many tabs open?
[1] https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
I really would love to see memory efficiency improve. I restarted FF yesterday and I'm already at 2.22 GB. It would be great to be able to set a ceiling on the amount of RAM FF is able to get its greedy little hands on. My iMac has 16GB, and I've seen FF reach half of that before when running a big Flash based web app with a hundred or so other tabs open. My little MacBook Air only has 4GB, so being able to tell FF to grab no more than 1GB or so would be fantastic!
Finally I have two blank desktops that tend to get eaten up by tabs that I use when people come into my office asking questions that I don't know the precise answer to off the top of my head.
But yes, on a single desktop about 12 tabs is my limit. And when I get over 4 full browser windows I start to get antsy and know that I can't possibly keep focused on everything I'm doing.
Why do you keep the tabs open after you've answered their question?
So, I have a lot of reference materials open on my desk, and I keep them open because finding the page I was on takes a long time, and loading that page takes even longer.
Some people might not know that it actually includes a feature specifically for this use case. If you start to type in a URL or page name similar to one already open in a tab, the awesomebar dropdown menu lets you jump to the already-opened tab.
And I'm not sure I really like it anyway - when I re-type a URL I'm usually looking to reload it to grab a fresh copy. I tab-complete the address of my development server and Hacker News very often; anything else I don't usually know the URL off the top of my head, I just remember that I have such and such doc on such and such desktop.
eg: % Firefox 7 memory
Meantime being careful about what I close does a decent job, and I don't have to maintain a proxy server.
One window with few tabs is for programming to-reads, second windows - with sites from searching for some item to buy, third - with stock information, etc. This way accumulating 100+ tabs is really not a big deal and it still remains manageable. Until FF crashes or, worse yet, grinds to a halt that is. "We are sorry, it is so embarrasing" it would say on a restart and then get herniated again trying to open all these tabs AT ONCE. Poor thing.
Go to about:config and set browser.sessionstore.resume_from_crash to false.
http://kb.mozillazine.org/Browser.sessionstore.resume_from_c...
Usually, I'll have about half a dozen windows open with about half a dozen tabs each. I group the tabs together so that each window holds similar tabs, so it's not really 30 things I'm keeping track of but more like 5-6. E.g. right now I have one window where I was checking finance related news, stock quotes, etc. One window with a bug report and several tabs open looking at relevant source code and google searches related to investigating the problem. I've got one window that's my mail. I've got one window with a few HN stories open.
You must be looking at very media heavy sites, then. Looking at Chrome's task manager (shift-escape opens it), my per-tab memory usage ranges between ~2.4MB (HN pages) to ~44MB (a youtube video). The root process is using 120MB, GPU process 50MB, and Flash 94MB. So, in total, for 20 tabs I'm using 545MB, or 27.25MB/tab. A far cry from "~100 MiB per tab".
Note that I'm on Windows 7 x64; while you may be entirely correct about Chrome on your platform of choice, it sounds like FUD to me.
VIRT RES SHR S %CPU %MEM TIME+ COMMAND
685m 110m 25m S 2 2.8 0:29.09 /opt/google/chrome/chrome
905m 74m 14m S 0 1.9 3:55.19 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJ
879m 63m 16m S 0 1.6 0:02.95 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJ
889m 57m 15m S 0 1.5 0:08.17 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJ
872m 46m 15m S 0 1.2 0:05.67 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJ
866m 36m 12m S 0 0.9 0:10.46 /opt/google/chrome/chrome --type=extension --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackup
850m 23m 11m S 2 0.6 0:19.67 /opt/google/chrome/chrome --type=extension --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackup
267m 13m 7100 S 0 0.4 0:00.05 /opt/google/chrome/chrome --type=zygote
222m 9000 2084 S 0 0.2 0:00.92 /opt/google/chrome/chromeI mean, I guess they could use a message queue between their thread for window chrome and page rendering, but I don't recall them ever mentioning anything about that in any dev journals that I used to read years ago.
1. "I left Firefox on overnight with three tabs open, and now it's using 3.1 GiB of memory. This browser is terrible! Yes, I do have dozens of low-quality extensions installed, so?"
2. "I started Firefox, and already it's using over 300 MiB! That's insane! Why would a web browser ever use that much? I'm switching to Chrome, it only uses 100 MiB. What do you mean, 'multiple processes'?"
There may in fact be genuine issues buried somewhere in the discussion, but they're hard to discern against the general background noise.
You're getting confused between Firefox and Chrome. Firefox has always been the browser of choice for the "tons of tabs" crowd, because Chrome's process-per-tab model breaks down when there's more than a few dozen open.For example, I have just over 70 tabs open right now, Firefox has been running for about a month, and it's at 1.1 GiB resident memory. Chrome becomes very unhappy under such circumstances (since it uses about ~100 MiB per tab), so I'm careful to only open a few tabs at a time.