Jorge Villalobos encouraged add-on authors to check for memory leaks on the official Mozilla add-ons blog.
The follow add-ons were downgraded to “preliminary review” status on AMO, giving them less visibility: QuickDrag, Yahoo Toolbar. The Yahoo Toolbar case is interesting; it is available on AMO, but only has 47,618 users there. But the number of installed copies is much larger than this. (I can’t say how much larger, because the exact numbers are not public knowledge.) So it’s clear that most people who have it installed got it elsewhere, probably directly from Yahoo. Given that AMO accounts for only a tiny fraction of the installations, the effect of the downgrade in AMO review status is negligible. Furthermore, Jorge’s attempts to contact Yahoo appear to have failed. Finally, the only other means we have for addressing add-ons with problems is block-listing them, but that would be overkill in this case. So we are at an impasse. It’s a frustrating situation!
Gecko and Firefox
Jonathan Kew added memory reporters for thebes font objects. With text-heavy pages open, these can account for 10s of MBs of memory.
Andrew McCreight fixed some shutdown leaks involving the XBL cache.
Igor Bukanov did something with JS principals that I won’t pretend to understand. This bug wasn’t marked with the MemShrink tag, but it gave good Talos results, reducing the number of malloc calls and the maximum heap size on several platforms.
This week’s bug counts:
- P1: 26 (-2/+4)
- P2: 131 (-1/+3)
- P3: 88 (-5/+1)
- Unprioritized: 0 (-0/+1)
Nothing spectacular there.