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.