Small world, I created a page referred to in the bug report :).
Yes, Chrome's memory management got better [1] and Firefox's got worse (at least relatively, they know about the problem and made some improvements [2], but meanwhile other browsers got even better).
It looks like while both Chrome and FF improved their garbage collectors, FF somehow got much higher memory consumption in the first place (growing memory in places where it really shouldn't - aforementioned array assignments or drawing into canvas).
-----
[1] I remember a period where Chrome was tuning their memory management, you would get very different performance between subsequent Chrome updates.
Yes, Chrome's memory management got better [1] and Firefox's got worse (at least relatively, they know about the problem and made some improvements [2], but meanwhile other browsers got even better).
It looks like while both Chrome and FF improved their garbage collectors, FF somehow got much higher memory consumption in the first place (growing memory in places where it really shouldn't - aforementioned array assignments or drawing into canvas).
-----
[1] I remember a period where Chrome was tuning their memory management, you would get very different performance between subsequent Chrome updates.
[2] http://hacks.mozilla.org/2010/01/javascript-speedups-in-fire...