DevTools/Features/Memory: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Memory Tooling Backend = == Summary == Ultimately, we want to be able to provide tools that give Firefox users answers to the following questions: # is my page taking a lot ...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= Memory | {| class="fullwidth-table" | ||
|- | |||
| style="font-weight: bold; background: #DDD;" | Feature | |||
| style="font-weight: bold; background: #DDD;" | Status | |||
| style="font-weight: bold; background: #DDD;" | ETA | |||
| style="font-weight: bold; background: #DDD;" | Owner | |||
|- | |||
<section begin="status" /> | |||
| [[DevTools/Features/Memory]] | |||
| {{StatusHealthy|status=exploratory coding}} | |||
| YYYY-MM-DD | |||
| Kevin Dangoor | |||
<section end="status" /> | |||
|- | |||
|} | |||
== Summary == | == Summary == | ||
| Line 18: | Line 32: | ||
== Release Requirements == | == Release Requirements == | ||
# | * Electrolysis-ready | ||
== Next Steps == | |||
* Finish exploratory work to determine implementation plan | |||
== Related Bugs & Dependencies == | |||
See the [http://mozilla.github.com/devtools/2011/status.html#memoryback status page]. | |||
== Team == | |||
* Dave Camp: lead developer | |||
* Jan (Honza) Odvarko: representing Firebug's interests | |||
* Kevin Dangoor: PM | |||
== Other Documentation == | |||
The [http://www.eclipse.org/mat/ 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. | |||
__NOTOC__ | |||
[[Category:Feature]] | |||
[[Category:Firefox]] | |||
[[Category:DevTools]] | |||
[[Category:Priority 1]] | |||
Revision as of 14:34, 1 April 2011
| 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:
- is my page taking a lot of memory?
- if it is, how do I fix it? (where is that memory going?)
- am I allocating too many objects? if so, where?
For the first stage, we need to identify:
- what information we can get from the system presently
- 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
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.