New issue
Advanced search Search tips

Issue 732908 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 24
Cc:
etienneb@chromium.org
keishi@chromium.org
erikc...@chromium.org
style-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Potential memory leak with StoredInvalidationSet (GMAIL)

Project Member Reported by etienneb@chromium.org, Jun 13 2017 
We are running a chrome version with the --enable-heap-profiling for a few days and collecting periodically collecting memory dumps. By diffing the memory dumps we can figure out the remaining objects allocated. They are typically incorrect memory management of memory leak.

The current tab was gmail running for multiple days.

The allocations stackframe are attached in the images.
bug1.png
81.6 KB View Download
bug2.png
73.1 KB View Download
B3.png
91.1 KB View Download

Comment 1 by etienneb@chromium.org, Jun 13 2017 

Allocated objects created under stack frame StoredInvalidationSet : ~500k objects.

Comment 2 by benhenry@chromium.org, Aug 2

Cc: -kei...@chromium.com keishi@chromium.org

Comment 3 by dtapu...@chromium.org, Aug 24

Components: Blink>MemoryAllocator>GarbageCollection Blink>CSS

Comment 4 by erikc...@chromium.org, Aug 24

Status: WontFix (was: Untriaged)
This is very old and comes from early heap profiling analysis. We no longer attempt to profile renderer processes.
►

Sign in to add a comment