Open Bug 933026 (rec-JS-mem-prof) Opened 11 years ago Updated 2 years ago

Recorded JS Memory Profile

Categories

(DevTools :: Memory, defect, P2)

Product:
DevTools
Component:
Memory
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

People

(Reporter: akratel, Unassigned)

References

Details

(Whiteboard: [User Story], [mockup])

User Story

As a web/app developer, I would like to be able to analyze the memory profile of my application:

Acceptance Criteria:
- Only my app memory profile is included
- Can see all of the JS Globals and DOM nodes 
- sortable by type
- sortable by counts
- sortable by number of references
- sortable by total size.

Note: this story corresponds to the classic object profile. 

May require User story splitting along DOM versus JS object/nodes.
As a web/app developer, I would like to be able to analyze the memory profile of my application: Acceptance Criteria: - Only my app memory profile is included - Can see all of the JS Globals and DOM nodes - sortable by type - sortable by counts - sortable by number of references - sortable by total size. Note: this story corresponds to the classic object profile. May require User story splitting along DOM versus JS object/nodes.
Flags: pm-scrub?
Component: Developer Tools → Developer Tools: User Stories
User Story: (updated)
From bug 625846#c13 - ability to sort by file the constructor is defined in. According to Fitzgen, if we enable allocation tracking during recording (should use a refresh after recording), we can also have allocation sites as well
Component: Developer Tools: User Stories → Developer Tools: Memory
Flags: pm-scrub?
Product: Firefox → DevTools
I think we only miss this part for now: "Can see all of the JS Globals and DOM nodes" Or rather we can see the DOM nodes but not their size yet. We have a bug for this but I don't have it at the moment, so I'm gonna keep this bug open for now.
Priority: -- → P2
bug 1474383 is the one I was talking about in comment 2.
Depends on: 1474383
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.