Closed Bug 1508527 Opened 9 months ago Closed 9 months ago
The memory reporter for Content
Blocking Log is wrong
47 bytes, text/x-phabricator-request
|Details | Review|
This is where we allocate new items into the hashtable: <https://searchfox.org/mozilla-central/rev/b03a62c3c82316e733a3b09622c1cb7e59f64cc3/dom/base/ContentBlockingLog.h#82> In order to measure the memory usage correctly, we should measure the memory usage of OriginData first. That includes the nsTArray itself, so then we need to measure the size of the array excluding this.
Summary: The memory reporter for ContentBlocking is wrong → The memory reporter for ContentBlockingLog is wrong
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/fd9a2224eb52 Fix the memory reporter for ContentBlockingLog r=baku
You need to log in before you can comment on or make changes to this bug.