Chrome 11 is such a hog
cubic-m.blogspot.com
cubic-m.blogspot.com
But I don't see the problem with large memory use. Ideally, all of your memory should be put to use all of the time, otherwise it is wasted, no? Shouldn't we be complaining that browsers aren't using more of our 4,6,8,12,16 gigs of RAM?
In my case, its not.
(Yes, yes, this attitude has ruined the software industry. Fine, use your slow but conservative-of-nearly-infinite-resource browser.)
The "typical" time for space tradeoff says otherwise. Exceptions abound of course, but I haven't seen your assertion hold up over the vast majority of algorithms.
For context, I already had opened Thunderbird, Sunbird, IRC, Skype, Pidgin, a twitter client, Audacious, an OpenOffice document and a spreadsheet, GIMP with 4 large and scribbled on photos, and a good number of terms and gvims.
Then I opened Chrome 11. And started opening tabs. After opening 101 tabs (really) spanning 3 windows, I gave up. I had it down to 110 MB physical RAM remaining, but it was slow going. These were real web content tabs of all different pages, not empty tabs. The system in general was still completely responsive, though Chrome was taking about 0.5 seconds to switch tabs as opposed to the normally instantaneous response.
So... whether Chrome 11 is a hog really seems to be somewhat system dependent. I do grant it's a significant download compared to the other browsers.
I'm going to go out on a limb and speculate that Safari uses more native Apple libs than Chrome, and those libs are resident already for the most part. This might account for your differences.