Platform/Features/RevampAboutMemory

From MozillaWiki
< Platform‎ | Features
Revision as of 02:56, 2 May 2011 by Nnethercote (talk | contribs) (Created page with "{| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; backgro...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Feature Status ETA Owner
Revamp about:memory Stage 1 needs super-review. 2011-05-06 Nicholas Nethercote

Summary

Greatly improve about:memory.

Team

Who's working on this?

  • Feature Manager: Nicholas Nethercote (nnethercote@mozilla.com, 'njn' on IRC)
  • Lead Developer: Nicholas Nethercote

Release Requirements

  • Stage 1: bug 633653.

After that, much of it can be done gradually, in a bug-by-bug fashion.

Next Steps & Open Issues

Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished. Including the name of who's responsible for each item, and a rough ETA can be useful.

Open issues include unanswered questions, things that need to be explored, decisions that still need to be made, etc. Again, including the name of who's responsible for each item can be useful.

Use Cases

about:memory should be the first place anyone looks for any problem or question related to memory usage. (In particular, it should subsume OS tools like 'top', 'ps' and the Windows Task Manager.) If it doesn't answer the question, then more advanced tools can be used.

In particular, it will be very useful in bug reports. People often currently say vague things like "Firefox was using 1GB of memory" without explaining how they got that number. By cutting + pasting about:memory things will be a lot clearer.

Designs

See screenshots in bug 633653 for stage 1.

Goals

  • Cutting + pasting the contents of about:memory into a text box should produce highly readable output.
  • Eventually, most interesting parts of memory (eg. the used part of the heap) should be marked as being owned by a particular part of the system.

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.