Re: Isolating each tab
>what Chrome is loading into those tabs
dumb question, but what is eating so much RAM on browsers?
If I quit Firefox and just reopen this article's main page, I am @ 450MB on a Mac already. Sure, you can blame FF for being a hog (I do), but start tallying up Chrome processes and...*
The text representation of an html page, including all its css and js can't account for much. You need to add the DOM tree, which I assume is a complex linked tree of some sorts. You add actual video mapping data for the display. CSS-to-dom-to-video tracking memory constructs. But still, many other apps are complex and not such huge hogs as browsers. Is this cached stuff, just in case you need to go back to a tab?
*Btw, being cynical, for Chrome this is probably a not-insignificant benefit of splitting into processes - hides RAM use somewhat.