DevTools/Features/Memory

Please use "Edit with form" above to edit this page.

Status

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

{{#set:Feature name=Memory tooling backend

|Feature stage=On hold |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}

Team

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)

{{#set:Feature product manager=Kevin Dangoor

|Feature feature manager=Kevin Dangoor |Feature lead engineer=Dave Camp |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Virgil Dicu |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature 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

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

• See the status page.

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |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. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=* Electrolysis-ready |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* See the status page. |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=Developer Tools |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=DevTools }}

Team status notes

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

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}

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.