Closed Bug 1062006 Opened 10 years ago Closed 9 years ago

e10s: Memory measurements reported by telemetry are only for the chrome process

Categories

(Toolkit :: Telemetry, defect, P3)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1198209
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: n.nethercote, Unassigned)

References

Details

(Whiteboard: [MemShrink:P2])

All the MEMORY_* telemetry measurements are measured in the parent process. When e10s is enabled, we'll be missing all the memory used by child processes.
tracking-e10s: --- → ?
Whiteboard: [MemShrink]
This might be subsumed by bug 1024021. Depends exactly how that bug is implemented, e.g. do we want parent and child process measurements to be added, or reported separately?
For the purposes of Win32 address space, the max of the two may be the most interesting, but generally we probably just want to add it up, in the current iteration of e10s that is just one parent and one child process for the most part.
Depends on: 1024021
Whiteboard: [MemShrink] → [MemShrink:P2]
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.