New issue
Advanced search Search tips

Issue 671653 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Feature



Sign in to add a comment

Chrome.dll should allocate its own heap

Project Member Reported by siggi@chromium.org, Dec 6 2016

Issue description

This will reduce contention on the heap (slightly), will make it easier to instrument Chrome's heap usage with existing Windows tools, and will make it easier to separate Chrome's own usage from the "systems".
 
Project Member

Comment 1 by bugdroid1@chromium.org, Dec 6 2016

Comment 2 by siggi@chromium.org, Dec 7 2016

Status: Started (was: Untriaged)
Keeping this bug open while I verify that this doesn't negatively affect memory usage metrics.
Project Member

Comment 3 by bugdroid1@chromium.org, Dec 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7fb93a524deced49ea1d5620479ea449dc0896e7

commit 7fb93a524deced49ea1d5620479ea449dc0896e7
Author: siggi <siggi@chromium.org>
Date: Mon Dec 12 22:22:15 2016

Iterate CRT heap instead of process heap.

BUG=671459, 671653 

Review-Url: https://codereview.chromium.org/2569753002
Cr-Commit-Position: refs/heads/master@{#437930}

[modify] https://crrev.com/7fb93a524deced49ea1d5620479ea449dc0896e7/content/renderer/render_thread_impl.cc

Comment 4 by siggi@chromium.org, Feb 9 2017

Status: Fixed (was: Started)

Sign in to add a comment