This specific case is not bloat at all though, it's actually you as a user having too much content that you care about. So I don't see why this is relevant at all.
It's not 'boat' per se but it's not caused by the user content. It's caused by chrome's process model. Firefox uses almost an order of magnitude less memory per tab.
