{"id":1926,"date":"2012-05-15T11:35:04","date_gmt":"2012-05-15T00:35:04","guid":{"rendered":"http:\/\/blog.mozilla.org\/nnethercote\/?p=1926"},"modified":"2012-05-15T11:35:04","modified_gmt":"2012-05-15T00:35:04","slug":"additional-update-on-leaky-add-ons","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/nnethercote\/2012\/05\/15\/additional-update-on-leaky-add-ons\/","title":{"rendered":"Additional Update on Leaky Add-ons"},"content":{"rendered":"<p>I <a href=\"http:\/\/blog.mozilla.org\/nnethercote\/2012\/05\/07\/update-on-leaky-add-ons\/\">wrote last week<\/a> about leaky add-ons.\u00a0 Specifically, Kyle Huey landed a patch that in most cases prevents zombie compartments, which are the most common kind of memory leak in add-ons.\u00a0 However, this change itself caused a different memory leak in some add-ons built with versions 1.3 and earlier of the Add-on SDK.\u00a0 I described this as &#8220;two steps forward, one step back&#8221;.<\/p>\n<p>Happily, Kyle landed a patch that <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=752877\">slightly delayed the cutting of the chrome-to-content references<\/a>.\u00a0 This has the following consequences.<\/p>\n<ul>\n<li>It doesn&#8217;t compromise the &#8220;two steps forward&#8221;.<\/li>\n<li>It fixes the &#8220;one step back&#8221;.<\/li>\n<li>It should reduce the potential for similar, as-yet-unknown backward steps.<\/li>\n<li>The <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=751466\">repacking of add-ons with newer versions of the Add-on SDK<\/a> is now less urgent than it was.\u00a0 It&#8217;s still a good idea, though, because older version had some other, albeit much smaller, leaks.<\/li>\n<\/ul>\n<p>This is good news.\u00a0 Firefox 15 is <a href=\"https:\/\/wiki.mozilla.org\/RapidRelease\/Calendar\">scheduled for release on August 28<\/a>.\u00a0 Assuming we don&#8217;t hit other problems with these changes prior to release, for users with add-ons there&#8217;s a good chance that Firefox 15 will use less memory and suffer fewer annoying pauses.<\/p>\n<p>Once again, it would be great if users of Nightly builds, particularly those that use add-ons, could pay attention to memory consumption and file bugs for any bad behaviour.\u00a0 Thanks!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I wrote last week about leaky add-ons.\u00a0 Specifically, Kyle Huey landed a patch that in most cases prevents zombie compartments, which are the most common kind of memory leak in add-ons.\u00a0 However, this change itself caused a different memory leak in some add-ons built with versions 1.3 and earlier of the Add-on SDK.\u00a0 I described [&hellip;]<\/p>\n","protected":false},"author":139,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[119,30,4546],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1926"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/users\/139"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/comments?post=1926"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1926\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/media?parent=1926"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/categories?post=1926"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/tags?post=1926"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}