Hmm. Maybe it's a FF add-on causing the problems for me, though I'm not using anything uncommon. An internal ps like chrome has might help pinning that down.
Chrome is definitely the RAM greedy one (and so many processes!), and always has been.
Strangely I can't find it in the latest dev release of chrome or chromium, it's still in stable. At least on linux, it also shows firefox's total memory usage, maybe they are doing lots of comparisons.
Chrome is definitely the RAM greedy one (and so many processes!), and always has been.