Current state of affairs:
Currently the code which computes effective sizes by performing computations on the graph of memory allocations is a part of the Catapult tracing tool.
Why this is a problem:
This has worked well to date but as we now wish to compute effective sizes to report to UMA/UKM. This means that we need to perform the graph processing in Chrome itself rather than relying on tracing to import and process traces.
How to fix this:
We will be porting and adapting the graph processing code in Catapult to Chrome's browser process as part of the memory instrumentation mojo service. This will then be consumed by UKM/UMA as well as the tracing system to obtain effective sizes.
Comment 1 by bugdroid1@chromium.org
, Oct 2 2017