If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Use a process-specific window ID in the window memory reporter

NEW
Unassigned

Status

()

Core
DOM
2 years ago
2 years ago

People

(Reporter: mccr8, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox42 affected)

Details

(Reporter)

Description

2 years ago
The window memory reporter in e10s uses the global window ID, which has the PID baked into the high bits. This isn't useful for a person reading the window memory reporter. This would require adding some new function, I guess on nsGlobalWindow, that would return the window ID without the PID, then using it in the reporter.
You need to log in before you can comment on or make changes to this bug.