[tracing] Add method to create "weak" global dumps
The renderer process could add memory dumps that are known to be non-existent in the browser. To resolve this issue, a notion of "weak" global allocator dump is introduced so that the renderer could tell it is unsure of the existence of the dump. A weak dump will be removed in the UI unless at least one process creates a non-weak global dump with the same guid. This would mark the existence of the memory. Sample use case: The browser creates a non-weak global dump and a renderer process creates a weak global dump for discardable segments. This represents the fact that the renderer doesn't know whether a segment is or isn't present in memory. BUG=570655 Review URL: https://codereview.chromium.org/1583483002 Cr-Commit-Position: refs/heads/master@{#370683}
Showing
Please register or sign in to comment