Marco Bonardo changed the Places JS services in a way that prevents certain kinds of SQLite connection leaks. As far as I can tell, this fixes leaks in the Delicious Bookmarks and CyberSearch add-ons.
Finally, Alexandre Poirot fixed a bug in the Add-on SDK that was causing zombie jetpack compartments in some cases when add-ons were disabled.
Hugh Nougher added a memory reporter for GPU memory on Windows 7 and Vista. See the “gpu-committed”, “gpu-dedicated” and “gpu-shared” entries in about:memory’s “Other Measurements” list.
Josh Aas implemented unloading for out-of-process plug-ins. If one is unused for 3 minutes it will be unloaded.
Andrew McCreight improved cycle collector dumping, which is useful in certain debugging cases.
Quote of the week
LifeHacker did some browser performance tests. Firefox 10 handily won the memory usage test, which involved loading sites in 9 tabs and then measuring. I personally think this is a pretty meaningless test, but I won’t complain about the good press.
As usual, the comments on the article featured a lot of debate about whether Firefox is a memory hog or not. One comment particular caught my attention:
They hardly used to be myths. I saw several times when old FF2x would be taking up over 1.4GB of RAM with just half a dozen tabs open.
Firefox 2 was released in October 2006, and superseded by Firefox 3 in June 2008. Bad reputations are really difficult to shake.
This week’s bug counts:
- P1: 26 (-0/+4)
- P2: 131 (-6/+3)
- P3: 76 (-2/+3)
- Unprioritized: 1 (-2/+1)