heap: Don't inject ObjectBitmap bit setting into HeapObjectHeader ctor
In the current design HeapObjectHeader sets ObjectStartBitmap in the constructor, which mixes abstractions and violates single responsibility principle, since ObjectStartBitmap is managed by a different entity - NormalPage. This patch decouples ObjectStartBitmap and HeapObjectHeader. Bug: 1029379 Change-Id: Iceb7450be7240d9b0765887b3e06663b56da7617 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002820 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#732560}
Showing
Please register or sign in to comment