{"id":1835,"date":"2012-03-14T14:36:47","date_gmt":"2012-03-14T03:36:47","guid":{"rendered":"http:\/\/blog.mozilla.org\/nnethercote\/?p=1835"},"modified":"2012-03-21T12:42:27","modified_gmt":"2012-03-21T01:42:27","slug":"memshrink-progress-week-39","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/nnethercote\/2012\/03\/14\/memshrink-progress-week-39\/","title":{"rendered":"MemShrink progress, week 39"},"content":{"rendered":"<h3>Add-ons<\/h3>\n<p>Versions of McAfee&#8217;s SiteAdvisor add-on prior to 3.4.1.195 <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=727938\">have been soft-blocked<\/a> due to an extreme memory leak.\u00a0 This means that it will be disabled within Firefox, but users can re-enable it if they want to.\u00a0 According to McAfee, most users should have been upgraded to 3.4.1.195 by now.\u00a0 Unfortunately, version 3.4.1.195 still has <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=729608\">some leaks<\/a>, and progress on fixing them has stalled.\u00a0 (If SiteAdvisor were an AMO add-on there&#8217;s a good chance it would have been downgraded to &#8220;preliminarily reviewed&#8221; by now.)<\/p>\n<p>Leaks in the <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=674535\">Lastpass<\/a>, <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=734097\">Fireshot<\/a>, and <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=735007\">Amabay<\/a> add-ons have been fixed.<\/p>\n<h3>Miscellaneous<\/h3>\n<p>Two weeks ago I <a href=\"http:\/\/blog.mozilla.org\/nnethercote\/2012\/02\/29\/memshrink-progress-week-37\/\">mentioned<\/a> that the not-yet-public areweslimyet.com detected a <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=731437\">large regression<\/a> in memory consumption caused by incremental garbage collection.\u00a0 Bill McCloskey <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=730853\">adjusted the GC and CC heuristics<\/a> in order to fix this.<\/p>\n<p>Justin Lebar previously added monitoring of available physical and virtual memory monitoring on Windows;\u00a0 if either goes below a threshold Firefox attempts to free up memory.\u00a0 This week he added <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=733495\">monitoring of available commit space<\/a>.<\/p>\n<p>When you switch to a new tab, decoded image data from the old tab is kept until a 20 second timer expires.\u00a0 This is a good idea because you might switch back to the original tab quickly.\u00a0 However, until this week, this don&#8217;t-discard-it-immediately behaviour was also used when a tab is closed!\u00a0 Justin Lebar landed a patch which separates these two cases, i.e. it <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=731419\">discards decoded image data immediately when a tab is closed<\/a>.<\/p>\n<p>I <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=713799\">tweaked the presentation of the &#8220;window-objects&#8221; sub-tree in about:memory<\/a> so that the memory used within each browser tab is more obvious.\u00a0 This is another step towards <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=687724\">true per-tab memory reporting<\/a>.\u00a0 Here&#8217;s an example for a tab in which I navigated first to valgrind.org and then to www.mozilla.org;\u00a0 the URL within the &#8220;top(&#8230;)&#8221; line is the one shown in the address bar.<\/p>\n<pre>\u2502\u00a0\u00a0 \u251c\u2500\u25001,933,824 B (02.68%) -- top(http:\/\/www.mozilla.org\/, id=13)\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u251c\u2500\u25001,497,480 B (02.08%) -- active\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u251c\u2500\u25001,496,456 B (02.08%) -- window(http:\/\/www.mozilla.org\/)\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0 \u251c\u2500\u2500\u2500\u2500876,912 B (01.22%) -- layout\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0\u00a0\u00a0 \u251c\u2500\u2500569,456 B (00.79%) \u2500\u2500 arenas\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0\u00a0\u00a0 \u251c\u2500\u2500238,224 B (00.33%) \u2500\u2500 style-sets\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0\u00a0\u00a0 \u2514\u2500\u2500\u250069,232 B (00.10%) \u2500\u2500 text-runs\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0 \u251c\u2500\u2500\u2500\u2500316,216 B (00.44%) \u2500\u2500 style-sheets\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2502\u00a0 \u2514\u2500\u2500\u2500\u2500303,328 B (00.42%) \u2500\u2500 dom [2]\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0 \u2514\u2500\u2500\u2500\u2500\u2500\u25001,024 B (00.00%) -- window([system])\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u2514\u2500\u25001,024 B (00.00%) \u2500\u2500 dom\r\n\u2502\u00a0\u00a0 \u2502\u00a0 \u2514\u2500\u2500\u2500\u2500436,344 B (00.61%) -- cached\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u2514\u2500\u2500436,344 B (00.61%) -- window(http:\/\/valgrind.org\/)\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u251c\u2500\u2500312,496 B (00.43%) -- layout\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u2502\u00a0 \u251c\u2500\u2500170,448 B (00.24%) \u2500\u2500 style-sets\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u2502\u00a0 \u251c\u2500\u2500125,040 B (00.17%) \u2500\u2500 arenas\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u2502\u00a0 \u2514\u2500\u2500\u250017,008 B (00.02%) \u2500\u2500 text-runs\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u251c\u2500\u2500\u250076,600 B (00.11%) \u2500\u2500 dom\r\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u2514\u2500\u2500\u250047,248 B (00.07%) \u2500\u2500 style-sheets<\/pre>\n<h3>Bug counts<\/h3>\n<p>This week\u2019s bug counts:<\/p>\n<ul>\n<li>P1: 24 (-5\/+0)<\/li>\n<li>P2: 132 (-2\/+3)<\/li>\n<li>P3: 92 (-1\/+6)<\/li>\n<li>Unprioritized: 0 (-1\/+0)<\/li>\n<\/ul>\n<p>We only had to triage five bugs in today&#8217;s MemShrink meeting.\u00a0 I don&#8217;t remember ever having such a small number.\u00a0 As a result, we spent some time reviewing the P1 bugs, and decided that several could be downgraded to P2 because the situation had improved in some fashion.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Add-ons Versions of McAfee&#8217;s SiteAdvisor add-on prior to 3.4.1.195 have been soft-blocked due to an extreme memory leak.\u00a0 This means that it will be disabled within Firefox, but users can re-enable it if they want to.\u00a0 According to McAfee, most users should have been upgraded to 3.4.1.195 by now.\u00a0 Unfortunately, version 3.4.1.195 still has some [&hellip;]<\/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,4544,4546],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1835"}],"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=1835"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1835\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/media?parent=1835"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/categories?post=1835"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/tags?post=1835"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}