Remove duplicated memory from Chrome |
|||||||
Issue descriptiondskiba@ is working on finding duplicated memory regions in the browser/renderer process. We should identify the source of the duplication and remove it. Email thread on project-trim: https://groups.google.com/a/chromium.org/d/topic/project-trim/EiKXwnbTvbo/discussion This is a tracking bug for the work.
,
Aug 5 2016
,
Aug 5 2016
,
Aug 5 2016
Filed issue 635041 for net::QuicStreamSequencerBuffer::QuicStreamSequencerBuffer (120 KiB).
,
Aug 5 2016
Filed issue 635142 for cc::ContiguousContainerBase::AllocateNewBufferForNextAllocation (98 KiB).
,
Aug 22 2016
,
Aug 24 2016
Filed issue 640698 about temporary duplication in DOMStorageArea. On DOMStorage-heavy sites (yahoo.com) that can be a significant number (1.4 MiB of duplicates) for noticeable time (~10 mins).
,
Sep 9 2016
Filed issue 642082 about duplicate DER certificate data (~190 KiB). Actually, the issue is (almost) fixed, I'm just slow linking it here.
,
Jan 9 2017
,
Aug 2 2017
Ping! This bug is assigned and has an owner, but hasn't been updated in over 180 days. Is this still something we want to do?
,
May 18 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by haraken@chromium.org
, Aug 5 2016