What's actually surprising is that it took them this many years to get it fixed. Memory fragmentation is just as bad as memory leaks. To the user, the RAM being used just keeps going up and up until they run out of memory and have to restart FF.
Could explain their recent flurries of rewriting the javascript jits.
[1]: https://www.ohloh.net/p/firefox/analyses/latest [2]: http://www.ohloh.net/p/chrome/analyses/latest
I hope they get it sorted out because it is the main blocker to getting a lot of the early adopter crowd who have switched to chrome back onto Firefox.
Also, I have flash disabled, and use 3 separate builds of chrome on OS X to separate web accounts, dev instances and anonymous browsing
> Memory fragmentation is just as bad as memory leaks.
Indeed.