Confirmed users
1,345
edits
Platform/Memory Reporting: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Nnethercote (talk | contribs) |
Nnethercote (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
'''tl;dr: You should read this document before writing a memory reporter. And please ask nnethercote to co-review any memory reporter patch.''' | |||
Mozilla code has infrastructure that lets different parts of the code report on their memory usage. This is most obviously used in about:memory and telemetry. This document describes things that you should know when writing a memory reporter. | Mozilla code has infrastructure that lets different parts of the code report on their memory usage. This is most obviously used in about:memory and telemetry. This document describes things that you should know when writing a memory reporter. | ||
| Line 172: | Line 174: | ||
It's important that no memory is measured twice; this can lead to very strange results in about:memory. Avoiding double measurement is easy in tree-like structures. In graph-like structures (where an object might be pointed to by more than one other object) it gets more difficult, and might even require some way to mark objects that have been counted (and then a way to unmark them once the measurement is complete). | It's important that no memory is measured twice; this can lead to very strange results in about:memory. Avoiding double measurement is easy in tree-like structures. In graph-like structures (where an object might be pointed to by more than one other object) it gets more difficult, and might even require some way to mark objects that have been counted (and then a way to unmark them once the measurement is complete). | ||
If you write a memory reporter, please get two people to review it: (a) someone who knows the data structures being measured, and (b) nnethercote, who can check for all the things covered by this document. Thanks! | |||
== DMD == | == DMD == | ||