Chrome.dll should allocate its own heap |
|||
Issue descriptionThis 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".
,
Dec 7 2016
Keeping this bug open while I verify that this doesn't negatively affect memory usage metrics.
,
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
,
Feb 9 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Dec 6 2016