{"id":1881,"date":"2012-04-18T17:37:02","date_gmt":"2012-04-18T06:37:02","guid":{"rendered":"http:\/\/blog.mozilla.org\/nnethercote\/?p=1881"},"modified":"2012-04-19T11:27:19","modified_gmt":"2012-04-19T00:27:19","slug":"memshrink-progress-week-43-44","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/nnethercote\/2012\/04\/18\/memshrink-progress-week-43-44\/","title":{"rendered":"MemShrink progress, week 43&#8211;44"},"content":{"rendered":"<p>As promised <a href=\"http:\/\/blog.mozilla.org\/nnethercote\/\">last time<\/a>, this MemShrink report covers two weeks&#8217; worth of activity.<\/p>\n<h3>Melbourne MemShrink Meet-up<\/h3>\n<p>This week Kyle Huey, Justin Lebar, Andrew McCreight, Jet Villegas flew to Melbourne to bunker down with me for a MemShrink work week.\u00a0 This is great for two reasons.\u00a0 First, it gives all of us an excuse\/opportunity to ignore the usual myriad of attention-grabbing tasks and focus solely on MemShrink stuff for a week.\u00a0 (For example, Jet is the manager of the layout team but he&#8217;s managed to do a couple of days of coding!)\u00a0 Second, it lets us collaborate and pick each others&#8217; brains much more easily and efficiently than normally.<\/p>\n<h3>Badd-ons<\/h3>\n<p>The following add-ons had zombie compartments fixed.<\/p>\n<ul>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=731801\">Yahoo! Toolbar<\/a>.\u00a0 This is a <em>very<\/em> widely-installed add-on.<\/li>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=729608\">McAfee SiteAdvisor<\/a>.\u00a0 This add-on previously had a <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=727938\">bad leak<\/a> which was mostly fixed a few weeks ago.\u00a0 This update fixes the remaining leaks.<\/li>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=734408\">Ant Video Downloader.<\/a> This is the 40th most popular add-on on AMO, with over 500,000 users.<\/li>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=730682\">Vimperator<\/a>.<\/li>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=737972\">Fastest Search<\/a>.<\/li>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=730682\">tubecheck.info<\/a>.<\/li>\n<li><a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=735766\">SeoQuake<\/a>.<\/li>\n<\/ul>\n<p>I&#8217;ve said before that add-on leaks are the #1 cause of high memory consumption in Firefox.\u00a0 Numerous add-ons have had leaks fixed, but this is a slow process.\u00a0 However, Kyle has been making good progress this week on a <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=695480\">patch<\/a> that has the potential to mitigate the majority of add-on leaks that cause zombie compartments.\u00a0 It currently passes all tests on try server and is undergoing review.\u00a0 Watch this space!<\/p>\n<p>Version 1.6 of the Add-on SDK was released, which <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=726485\">fixed all remaining known leaks<\/a>.\u00a0 Except that a new leak was found shortly before release!\u00a0 This was found too late to be fixed before the deadline for 1.6, but fortunately, it was quickly <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=740689\">fixed in version 1.6.1<\/a>.\u00a0 The Add-on SDK developers (especially Alexandre Poirot) have fixed a ton of leaks in the past few months, so it&#8217;s great to see this milestone reached.<\/p>\n<h3>Miscellaneous<\/h3>\n<p>Olli Pettay <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=743178\">fixed a leak relating to event listeners<\/a>.<\/p>\n<p>Henrik Skupin released <a href=\"http:\/\/www.hskupin.info\/2012\/04\/07\/memchaser-0-3-is-out\/\">version 0.3 of the MemChaser add-on<\/a>.\u00a0 It features improvements to the UI and the logging.<\/p>\n<p>Jonathan Kew <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=710727\">optimized the representation of font character maps<\/a>.\u00a0 Depending on the platform, this can save around 1MB of memory, or more if you have lots of fonts installed.<\/p>\n<p>Jared Wein landed an option for <a href=\"http:\/\/msujaws.wordpress.com\/2012\/04\/11\/opting-in-to-plugins-in-firefox\/\">making plugin content click-to-play<\/a>.\u00a0 This isn&#8217;t marked as a MemShrink bug but if a user can ignore such content, it has the potential to reduce memory consumption significantly in some cases.<\/p>\n<h3>Bug counts<\/h3>\n<p>Here are the current bug counts.<\/p>\n<ul>\n<li>P1: 22 (-1\/+2)<\/li>\n<li>P2: 84 (-56\/+3)<\/li>\n<li>P3: 100 (-8\/+18)<\/li>\n<li>Unprioritized: 0 (-1\/+0)<\/li>\n<\/ul>\n<p>Lots of movement there.\u00a0 This is because we&#8217;ve been going through the P2 bugs and closed a lot of them because they were dups, or lacked enough information to do anything useful, or we decided they were no longer worthwhile.\u00a0 We also downgraded quite a few P2 bugs to P3.\u00a0 As a result, the P2 list is much more interesting than it was.\u00a0 And we&#8217;re only partway through it!<\/p>\n<h3>A new meeting schedule<\/h3>\n<p>I mentioned last time that I would be writing these reports every two weeks from now on, instead of weekly.\u00a0 Similarly, we&#8217;ve decided to reduce the frequency of MemShrink meetings to once every two weeks.\u00a0 The next meeting will be on May 1st.<\/p>\n<p>This change does not reflect a reduction in the amount of work being done on MemShrink bugs.\u00a0 Rather, it reflects a reduction in the number of new MemShrink bugs being filed.\u00a0 At the past few meetings we&#8217;ve had only a handful of new bugs each time and triage has only taken a few minutes.\u00a0 (In comparison, in the early days of MemShrink, several times we didn&#8217;t get through all the new bugs in an hour.)<\/p>\n<p>This leaves us lots of time for talking about other things;\u00a0 in fact, more time than we&#8217;ve needed.\u00a0 And time spent in meetings is time not spent fixing problems, so this feels like the right thing to do.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As promised last time, this MemShrink report covers two weeks&#8217; worth of activity. Melbourne MemShrink Meet-up This week Kyle Huey, Justin Lebar, Andrew McCreight, Jet Villegas flew to Melbourne to bunker down with me for a MemShrink work week.\u00a0 This is great for two reasons.\u00a0 First, it gives all of us an excuse\/opportunity to ignore [&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,4544,4546],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1881"}],"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=1881"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1881\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/media?parent=1881"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/categories?post=1881"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/tags?post=1881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}