heap: Fix misaccounting of allocated-object-size
When shrinking/promptly-freeing/expansion happens, memory occupied by linear allocation area is already accounted (in SetAllocationPoint()). Object shrinking case: Expanding the area means that the bytes stay allocated. Object expansion case: Just using up space that's accounted for. Bug: 1029379 Change-Id: I77edced5e71b989d6968f92a5bbf0bd4819aea7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051263 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#740723}
Showing
Please register or sign in to comment