Commit b6a2b438 authored by hpayer's avatar hpayer Committed by Commit bot

[heap] Do not use the high memory watermark for committed memory accounting in large object space.

BUG=

Review-Url: https://codereview.chromium.org/2019333009
Cr-Commit-Position: refs/heads/master@{#36650}
parent 471893cc
...@@ -2988,14 +2988,10 @@ AllocationResult LargeObjectSpace::AllocateRaw(int object_size, ...@@ -2988,14 +2988,10 @@ AllocationResult LargeObjectSpace::AllocateRaw(int object_size,
size_t LargeObjectSpace::CommittedPhysicalMemory() { size_t LargeObjectSpace::CommittedPhysicalMemory() {
if (!base::VirtualMemory::HasLazyCommits()) return CommittedMemory(); // On a platform that provides lazy committing of memory, we over-account
size_t size = 0; // the actually committed memory. There is no easy way right now to support
LargePage* current = first_page_; // precise accounting of committed memory in large object space.
while (current != NULL) { return CommittedMemory();
size += current->CommittedPhysicalMemory();
current = current->next_page();
}
return size;
} }
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment