This is a main reason I don't use Chrome. Since each tab is running under a sep process, there is no easy way to tell how much total memory is being used. Despite all the improvements, Firefox still has some pretty bad memory leaks and often runs over a gig of memory with just 5 or 6 tabs open. If they go this route, mem leaks will be harder to spot.
>This is a main reason I don't use Chrome. Since each tab is running under a sep process, there is no easy way to tell how much total memory is being used.
Seeing "how much memory is being used" is a major use case for you using a browser?
If a browsers works fast and doesn't leak memory, one shouldn't care how much memory exactly is used.
> If a browsers works fast and doesn't leak memory, one shouldn't care how much memory exactly is used.
That's a big assumption. Realistically speaking, there's only FF, Safari, and Chrome. FF leaks like crazy (sometimes on it's own but sometimes it could be a plugin). Safari doesn't support all the plugins I use and Chrome may but I'm don't like their dev console layout. And if you don't see how much mem is being used, you have no way of telling if a newly installed plugin just caused a memory leak (unless it just totally prevents you from using the browser).
> Seeing "how much memory is being used" is a major use case for you using a browser?
Yes, certainly. My development machine has 8 GB of RAM. On a number of occasions I've recovered from a marginal memory problem/commencement of disk swap by dumping Chrome. I should have more RAM, but still.
Chrome uses a lot of memory. Unless you have a ridiculous amount of RAM, there will be times when you'll notice the load.
> If a browsers works fast and doesn't leak memory, one shouldn't care how much memory exactly is used.
