Declaring reportMemoryUsage as a friend of HashSet and HashTable is considered harmful, so we should switch to using only public API of the classes. This way we will still be able to collect necessary information. The problem is that it will be easier to change the implementation and forget to update the instrumentation(which is probably fine since these classes don't change often), also we won't be able to automatically mark corresponding objects in the memory as instrumented while checking correctness of the memory instrumentation.
Created attachment 166187 [details] Patch
Comment on attachment 166187 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=166187&action=review lgtm > Source/WebKit/chromium/ChangeLog:8 > + Updatee the test for HashSet memory instrumentation. We don't add typo: Updatee
Comment on attachment 166187 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=166187&action=review >> Source/WebKit/chromium/ChangeLog:8 >> + Updatee the test for HashSet memory instrumentation. We don't add > > typo: Updatee Done.
Committed r129875: <http://trac.webkit.org/changeset/129875>