The big news this week is that Kyle Huey made chrome-to-content leaks impossible<\/a>.\u00a0 Kyle wrote about this in some detail<\/a>.\u00a0 This particular kind of leak can happen in Firefox, but more importantly, it’s responsible for most of the leaks in add-ons that we know about<\/a>.\u00a0 In other words, it should greatly reduce the problem of leaky add-ons, a problem I previously identified as the #1 MemShrink issue<\/a>.\u00a0 It’ll take a while to see the exact effects and whether they match expectations.\u00a0 Nonetheless, this is a big deal<\/a>!<\/p>\n Olli Pettay fixed a leak relating to Geolocation<\/a>.<\/p>\n The following add-ons had leaks fixed: Collusion<\/a>, SearchMenu<\/a>, panchang<\/a>, HTML5 Extension for Windows Media Player Firefox Plug-in<\/a>.<\/p>\n I reduced the size of JSScripts (here<\/a>, here<\/a> and here<\/a>).\u00a0 This increased the number of JSScripts that fit in a GC arena from 31 to 42 (on 32-bit platforms) and from 19 to 28 (on 64-bit platforms).\u00a0 This reduced the size of the “scripts” entry in about:memory — which is often multiple MB for the compartments of complex web sites and apps like Gmail — by approximately 30%.\u00a0 (The final two patches in the sequence are being held up by the current tree closure<\/a>, but will land as soon as that has passed.)<\/p>\n Nathan Froyd reduced the size of mozilla::dom::Link — one of which exists for every <a> or <link> or <area> element shown in a page — by 4 bytes (on 32-bit platforms) and 8 bytes (on 64-bit platforms).<\/p>\n Ehsan Akhgari reduced the size of nsEditor — one of which exists for each text area in a page, and some other places — by 16 bytes on 64-bit platforms.<\/p>\nSlimmer data structures<\/h3>\n
\u00a0Quote of the FORTNIGHT<\/h3>\n