[PM] Fix memory leak when WebMemoryAggregator gets no result
Make WebMemoryAggregator owned by its callback instead of by itself so that it is also deleted if the callback is dropped. R=ulan Bug: 1085129 Change-Id: I4a7dcdd208c1b02933cf9e94cfcc6bd84502b3ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515042Reviewed-by:Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#823547}
Showing
Please register or sign in to comment