[citation][nom]cTs Corvette[/nom]Then the solution would be "don't open so many tabs." There's this cool feature built into the tabs in Chrome, maybe you've never noticed it, but each open tab has an "x" on the right side of it. If you click it, the tab closes. Personally, I think they should call it the "Tab Nanny" instead. "Tab assassin" sounds like something cool instead of something to pacify the people who are too lazy to click an x.[/citation]
Not everyone always has that option. I often use a few dozen tabs that I have to flip through for some things and on my laptop with only 2GB of RAM, I really have to watch my memory usage. Instead of closing tabs, I even occasionally kill their process through the task manager if I'm not using them now, but will use them soon and need more memory right now.
[citation][nom]Pherule[/nom]If I have tabs open they're open for a reason. If I'm done with them I will manually close them.I'm sure Firefox already has this functionality with an extension, so Google trying to patent something that already exists is utter crud.Hey Chrome developers, I have an idea! Make the --single-process command switch work again. Multi-process browsers are no good to me until I get 32GB memory and a 64-bit OS.[/citation]
I could be wrong, but I don't recall Firefox (even through third party extensions) having this feature. However, Firefox doesn't need it, so that's not a major loss.
[citation][nom]in_the_loop[/nom]I disagree. Chrome use an insane amount of memory when you have a lot of tabs open. Remember that each tab gets its own process and dedicated memory (whcih also makes Chrome more stable since it is the only thing crashing)It is very easy to exceed 2 GB of memory usage with many tabs open i chrome (especially withy youtube sessions with multiple tabs).On a laptop with 2-3 Gigs of memory that is making it crawl really slowly.In fact, it is the reason for me not using chrome at all on my laptop and ujse firefox instead.(I use Chrome on my desktop though which has plenty of memory).And there are plugins that adress this problem so there is a demand for it, but these plug-ins work very poorly, so it is a good thing that google is adressing this!They wouldn't do it if it wasn't needed, and it is, since the plugs works so poorly and many still use computers with too little memory in them![/citation]
Actually, Chrome does not give each tab its own process, but gives tab groups their own processes (not even always related tabs, sometimes it just seems to group tabs randomly into processes). It's not quite the same.