4 ms·
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. Despi
by reubano 12y ago
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.
- kalmi10 12y agoChrome has a built-in Task Manager (Shift+Esc). One can even see the memory consumption and CPU usage of each tab and extension.
- reubano 12y agoThat doesn't work for me on a mac. But what about total usage? If I have to add up the mem used for each tab it won't be helpful.
- grrowl 12y agoFind it under Window > Task Manager, or detailed memory usage information by navigating to "chrome://memory" The latter displays total memory usage at the top of the page. edit: As child poster noted, total memory is overcounted as it seems to be quite difficult to audit exactly what memory is shared within each child process. (see https://code.google.com/p/chromium/issues/detail?id=25454 https://code.google.com/p/chromium/issues/detail?id=25454 )
- reubano 12y ago"Note: This page will show memory use for all running browsers, not just Chrome. (Bug: We seriously overcount our own memory usage: Issue 25454.)"
- coldtea 12y ago>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.
- lutusp 12y ago> 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.
- reubano 12y ago> 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).