This is a major milestone for the MemShrink project.\u00a0 It shows the progress we have made (MemShrink started in earnest in June 2011) and will let us identify regressions more easily.<\/p>\n John’s done a wonderful job implementing the site.\u00a0 It has lots of functionality:\u00a0 there are multiple graphs, you can zoom in on parts of graphs to see more detail, and you can see revisions, dates and about:memory snapshots for individual runs.<\/p>\n John has also put in a great deal of work refining the methodology to the point where we believe it provides a reasonable facsimile of real-world browsing;\u00a0 please read the FAQ<\/a> to understand exactly what is being measured.\u00a0 Many thanks also to Dave Hunt and the QA team for their work on the Mozmill Endurance Tests<\/a>, which are at the core of AWSY’s testing.<\/p>\n Update:<\/strong> Hacker News has reported on this<\/a>.<\/p>\n Frequent readers of this blog will be familiar with zombie compartments<\/a>, which are JavaScript compartments that have leaked, due to defects in Firefox or add-ons.\u00a0 Windows (i.e. Justin Lebar has introduced the notion of “ghost windows”.\u00a0 A ghost window is one that meets the following criteria.<\/p>\n The basic idea is that a ghost window has a high chance of representing a genuine leak, and this automated identification of suspicious windows will make leak detection simpler.\u00a0 Justin has added ghost window tracking to about:memory<\/a>, about:compartments<\/a>, and telemetry<\/a>.\u00a0 (These three bugs were all marked as MemShrink:P1.)\u00a0 Ghost window tracking is mostly untested right now, but hopefully it will become another powerful tool for finding memory leaks.<\/p>\n We’ve been tracking leaky add-ons<\/a> in Bugzilla for a while now, but we’ve never had a good product\/component to put them in.\u00a0 David Lawrence, Byron Jones, Stormy Peters and I have together created a new “Add-ons” component under the “Tech Evangelism” product<\/a>.\u00a0 The rationale for putting it under “Tech Evangelism” is that it nicely matches the existing meaning of that phrase — it’s a case where a non-Mozilla entity is writing defective code that interacts with Firefox and hurts users’ experiences with and perceptions of Firefox, and Mozilla can only inform, educate and encourage fixes in that defective code.\u00a0 This component is only intended for certain classes of common defects (such as leaks) that Mozilla contributors are tracking.\u00a0 It is not intended for vanilla add-on bugs;\u00a0 as now, they should be reported through whatever bug-reporting mechanism each add-on uses.\u00a0 I’ve updated the existing open bugs that track leaky add-ons to use this new component.<\/p>\n Leaks in the following add-ons were fixed:\u00a0 Video DownloadHelper<\/a> (the 2nd most popular add-on on AMO!), Scrapbook Plus<\/a>, Amazon Price Tracker.<\/a><\/p>\n This week\u2019s bug counts:<\/p>\n Good progress on the P1 bugs!<\/p>\n Many of the weekly MemShrink reports lately have been brief.\u00a0 From now on I plan to write a report every two weeks.\u00a0 This will make things easier for me and will also ensure each report is packed full of interesting things.\u00a0 See you again in two weeks!<\/p>\n","protected":false},"excerpt":{"rendered":" \u00a0Are we slim yet? John’s Schoenick’s areweslimyet.com (AWSY) has had its password removed and is now open to the public! This is a major milestone for the MemShrink project.\u00a0 It shows the progress we have made (MemShrink started in earnest in June 2011) and will let us identify regressions more easily. John’s done a wonderful […]<\/p>\n","protected":false},"author":139,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15267,4550,119,4554,30,4544,4546],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1861"}],"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=1861"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/posts\/1861\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/media?parent=1861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/categories?post=1861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/nnethercote\/wp-json\/wp\/v2\/tags?post=1861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"areweslimyet.com](\"http:\/\/blog.mozilla.org\/nnethercote\/files\/2012\/04\/AWSY-1024x737.png\" "\\"AWSY\\"")
<\/a><\/p>\nGhost windows<\/h3>\n
window<\/code> objects) can also be leaked, and often defects that cause compartments leaks will cause window leaks as well.<\/p>\n\n
Add-ons<\/h3>\n
Bug counts<\/h3>\n
\n
A new reporting schedule<\/h3>\n