[PM] Make WebMemoryAggregator report 0 bytes for cross-process frames.
This conflicts with the use of 0 bytes as a sentinel for frames that hadn't been measured and should be dropped from the result. So this also makes the bytes optional in WebMemoryBreakdownEntry, so that frames with a byte count of 0 are reported and frames without a byte count are dropped from the result. R=ulan Bug: 1085129 Change-Id: Ie838c72049465e3a3bef9c0a9bb3a11aa648e62c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616818Reviewed-by:Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#841480}
Showing
Please register or sign in to comment