New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 766394 link

Starred by 1 user
Status: WontFix
Owner:
█ brettw@chromium.org
Last visit 25 days ago
Closed: Jan 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

OOP memory logging should GC before recording a renderer dump

Project Member Reported by brettw@chromium.org, Sep 19 2017 
Oilpan allocations (and any other allocations it depends on) might be deletable but we haven't run GC yet.

Tracing currently forces a GC before dumping any oilpan allocations.

If we want to add this, we will need to force a GC, flush the memlog send buffers, and synchronize the dump in the profiling process to after the flush.

Comment 1 by brettw@chromium.org, Sep 19 2017 

Current one uses kTakeSnapshot which doesn't actually free anything (since it doesn't want to actually affect the behavior of the system).

Comment 2 by erikc...@chromium.org, Jan 11 2018

Status: WontFix (was: Assigned)
I'm less sure about this - doing a memory dump changes the system being profiled. Then we might run into cases where teh system is bloated until we do a heap dump, which never catches the bloat.
►

Sign in to add a comment