From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Memory tooling backend
Stage On hold
Status `
Release target `
Health OK
Status note `


Product manager Kevin Dangoor
Directly Responsible Individual Kevin Dangoor
Lead engineer Dave Camp
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Virgil Dicu
UX lead `
Product marketing lead `
Operations lead `
Additional members Jan (Honza) Odvarko (firebug representative)

Open issues/risks


Stage 1: Definition

1. Feature overview

Ultimately, we want to be able to provide tools that give Firefox users answers to the following questions:

  1. is my page taking a lot of memory?
  2. if it is, how do I fix it? (where is that memory going?)
  3. am I allocating too many objects? if so, where?

For the first stage, we need to identify:

  1. what information we can get from the system presently
  2. what work needs to be done to get the information required to answer the questions above

The goal of this project now is to get the ball rolling so that the backend can provide the information we want so that a future release can provide the user-visible tooling.

2. Users & use cases


3. Dependencies


4. Requirements

  • Electrolysis-ready



Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan


8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation

Stage 5: Release

10. Landing criteria


Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap Developer Tools
Secondary roadmap `
Feature list Platform
Project `
Engineering team DevTools

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

Other Documentation

The Eclipse Memory Analyzer Tool provides comprehensive views into memory usage on the Java platform. Ideally, we would provide more distilled information than this, but the MAT represents a much more robust tool than anything we've seen for JavaScript presently.