> 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 oc

> 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. Not really. Not if you care about performance.