Add RequestPrivateMemoryFootprint method to MemoryInstrumentation.
Most clients only need private memory footprint, but the existing methods would still query all the MemoryDumpProviders and then filter the results. This CL adds a new method that avoids querying MemoryDumpProviders. Bug: 851712 Change-Id: I269be2b5a74c32205ba6f4087a9bb8affb9cffb6 Reviewed-on: https://chromium-review.googlesource.com/1098623Reviewed-by:Primiano Tucci <primiano@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#567417}
Showing
Please register or sign in to comment