DevTools/Features/Memory

Feature	Status	ETA	Owner
DevTools/Features/Memory	exploratory coding	YYYY-MM-DD	Kevin Dangoor

Summary

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.

Release Requirements

• Electrolysis-ready

Next Steps

• Finish exploratory work to determine implementation plan

Related Bugs & Dependencies

See the status page.

Team

• Dave Camp: lead developer
• Jan (Honza) Odvarko: representing Firebug's interests
• Kevin Dangoor: PM
• George Carstoiu (irc:GeorgeCarstoiu): QA contact

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.