{"id":1823,"date":"2012-03-07T10:53:00","date_gmt":"2012-03-06T23:53:00","guid":{"rendered":"http:\/\/blog.mozilla.org\/nnethercote\/?p=1823"},"modified":"2012-03-07T10:53:00","modified_gmt":"2012-03-06T23:53:00","slug":"memshrink-progress-week-38","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/nnethercote\/2012\/03\/07\/memshrink-progress-week-38\/","title":{"rendered":"MemShrink progress, week 38"},"content":{"rendered":"

After last week’s action<\/a>, this week was quieter for MemShrink.<\/p>\n

Add-ons<\/h3>\n

I mentioned last week the plan to test the top 100 add-ons for memory leaks.\u00a0 Unfortunately we learned this week that the list I gathered is the top 100 installed<\/em> add-ons, not the top 100 enabled<\/em> add-ons.\u00a0 It’s quite possible that a lot of installed “third-party” add-ons (those installed by a program outside of Firefox, such as anti-virus programs) are disabled, in which case this top 100 list won’t reflect actual usage.<\/p>\n

As a result, the top 100 testing is on hold until we can resolve this issue.\u00a0 Telemetry data<\/a> may help, though that data might exhibit opt-in biases.\u00a0 I’m also going to investigate the possibility of changing the daily ping to distinguish between enabled and disabled add-ons, which would give us fully representative data.<\/p>\n

Landed patches<\/h3>\n

I merged the “dom+style” and “layout” trees in about:memory<\/a>.\u00a0 This is a step towards per-tab memory reporting<\/a>.\u00a0 It also probably breaks about:nosy<\/a> \ud83d\ude41<\/p>\n

I also converted the DOM memory reporters to the new style<\/a>, added measurement of URIs and links<\/a>, and added measurement of the FramePropertyTable<\/a>.\u00a0 These changes reduced about:memory’s “heap-unclassified” by several MBs in common cases.<\/p>\n

Bill McCloskey changed the GC marker stack so it shrinks periodically<\/a>.\u00a0 Previously it could grow from 256KB to over 2MB and would never be shrunk once that happened.<\/p>\n

Bug counts<\/h3>\n

This week\u2019s bug counts:<\/p>\n

    \n
  • P1: 29 (-0\/+1)<\/li>\n
  • P2: 131 (-4\/+6)<\/li>\n
  • P3: 87 (-3\/+7)<\/li>\n
  • Unprioritized: 1 (-2\/+1)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

    After last week’s action, this week was quieter for MemShrink. Add-ons I mentioned last week the plan to test the top 100 add-ons for memory leaks.\u00a0 Unfortunately we learned this week that the list I gathered is the top 100 installed add-ons, not the top 100 enabled add-ons.\u00a0 It’s quite possible that a lot of […]<\/p>\n","protected":false},"author":139,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4550,119,30,4544,4546],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1823"}],"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=1823"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1823\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/media?parent=1823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/categories?post=1823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/tags?post=1823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}