Closed
Bug 661412
Opened 13 years ago
Closed 13 years ago
Update telemetry memory reporters
Categories
(Toolkit :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: taras.mozilla, Assigned: taras.mozilla)
References
Details
Attachments
(1 file)
(deleted),
patch
|
n.nethercote
:
review+
|
Details | Diff | Splinter Review |
about:memory recently changed. Telemetry can no longer find memory fields it's looking for. I also updated the ranges to match what people were submitting.
Attachment #536778 -
Flags: review?(nnethercote)
![]() |
||
Comment 1•13 years ago
|
||
Comment on attachment 536778 [details] [diff] [review] updated probes Review of attachment 536778 [details] [diff] [review]: ----------------------------------------------------------------- Looks fine. BTW, I personally think the two most interesting measurements are "explicit" and "resident"; bug 660731 is open to make them easier to get from JS code.
Attachment #536778 -
Flags: review?(nnethercote) → review+
Assignee | ||
Comment 2•13 years ago
|
||
Replaced heap-used with resident. Can add explicit once that lands. http://hg.mozilla.org/mozilla-central/rev/fabceeb16a3d
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
+ "explicit/layout/all": [1024, 64 * 1025, 10] Should that be 64 * 1024?
Assignee | ||
Comment 4•13 years ago
|
||
(In reply to comment #3) > + "explicit/layout/all": [1024, 64 * 1025, 10] > > Should that be 64 * 1024? yup, fixed that in the above commit
(In reply to comment #4) > (In reply to comment #3) > > + "explicit/layout/all": [1024, 64 * 1025, 10] > > > > Should that be 64 * 1024? > > yup, fixed that in the above commit I can't see where you changed it. http://mxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/TelemetryPing.js#59 "explicit/layout/all": [1024, 64 * 1025, 10]
Assignee | ||
Comment 6•13 years ago
|
||
Sorry. Looks like I only fixed it locally here. I'll fix it in the next set of telemetry patches. Thanks for doublechecking.
Updated•13 years ago
|
Assignee: nobody → tglek
You need to log in
before you can comment on or make changes to this bug.
Description
•