Closed
Bug 1689182
Opened 5 years ago
Closed 5 years ago
Collect resident unique set size for MemoryTelemetry from the parent process
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
87 Branch
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
We're currently waking each content process, including preallocated ones which should be idle, on a regular basis due to the parent process asking it to collect its current resident unique set size. This is possible to do from the parent process without waking content since bug 1652813. See bug 1689164 for more details.
Comment 1•5 years ago
|
||
Note that we'll want to be sure to do this from a background thread, since these computations can sometimes be pretty slow and expensive.
Assignee | ||
Comment 2•5 years ago
|
||
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2da0de3af357
Collect content memory telemetry from the parent process, r=kmag
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox87:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•