As a security precaution, we have turned on the setting "Require API key authentication for API requests" for everyone. If this has broken something, please contact
Last Comment Bug 705602 - Use mallocSizeOf in prefixset memory reporter
: Use mallocSizeOf in prefixset memory reporter
Product: Toolkit
Classification: Components
Component: Safe Browsing (show other bugs)
: unspecified
: All All
: -- normal (vote)
: Firefox 11
Assigned To: Nicholas Nethercote [:njn]
Depends on:
Blocks: 707865
  Show dependency treegraph
Reported: 2011-11-27 21:37 PST by Nicholas Nethercote [:njn]
Modified: 2014-05-27 12:25 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

patch (4.26 KB, patch)
2011-11-27 21:37 PST, Nicholas Nethercote [:njn]
gpascutto: review+
Details | Diff | Splinter Review

Description User image Nicholas Nethercote [:njn] 2011-11-27 21:37:22 PST
Created attachment 577193 [details] [diff] [review]

I'm converting existing memory reporters to use mallocSizeOf.  See for details about why I'm doing this.

This patch changes the "prefixset" memory reporter accordingly.  As part of this change, I removed nsUrlClassifierPrefixSet::SizeOfIncludingThis from the IDL, because there's no need for SizeOf-style functions to be exposed via IDL;  no other such functions are exposed in this way.  That change simplifies it significantly.
Comment 1 User image Nicholas Nethercote [:njn] 2011-12-08 14:01:54 PST
Gian-Carlo, can you do this review soon?  It's a very small patch and it's blocking several pieces of my memory reporter work.  Thanks!
Comment 2 User image Gian-Carlo Pascutto [:gcp] 2011-12-08 23:22:10 PST
Comment on attachment 577193 [details] [diff] [review]

You changed the UUID without updating everything. You'll need to update toolkit/components/build/nsToolkitCompsCID.h as well or things are going to break.

r+ if that is fixed.
Comment 3 User image Nicholas Nethercote [:njn] 2011-12-15 16:34:10 PST
Comment 4 User image :Ms2ger (⌚ UTC+1/+2) 2011-12-16 05:48:03 PST

Note You need to log in before you can comment on or make changes to this bug.