New issue
Advanced search Search tips

Issue 716304 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Apr 2017
Cc:
tasak@google.com
keishi@chromium.org
haraken@chromium.org
erikc...@chromium.org
bashi@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Renderer processes keep growing in memory

Project Member Reported by ssid@chromium.org, Apr 28 2017 
This is not a regression, but an usual scenario of Chrome user. So, I have 2 traces with heap profiling enabled on Chrome canary. One after running Chrome for a week and one after closing and re-opening the same tabs again. The difference is 2GB on PSS.

It looks like gmail has grown by 500MB and sheets and docs too by a smaller number. All of partition alloc, blinkgc, v8 and malloc have grown in the renderers.

Why does it keep growing? Is it the fault of the websites or Chrome?
trace_my_browser_same_tab_start.json.gz
8.5 MB Download
trace_my_browser_week (1).json.gz
9.6 MB Download

Comment 1 by bashi@chromium.org, Apr 28 2017

Cc: keishi@chromium.org tasak@google.com

Comment 2 by keishi@chromium.org, Apr 28 2017 

The traces were taken using 58.0.3029.14 which does not contain the fix for crbug.com/2809183003 so I think that's the problem.
Before the fix LiveNodeLists were retained by the Document instead of the Element leading to bloat that is particularly bad on long living SPAs.

Comment 3 by bashi@chromium.org, Apr 28 2017 

Probably crrev.com/2809183003 ?

Comment 4 by keishi@chromium.org, Apr 28 2017 

Oh yes crrev.com/2809183003 and in case of M58 it was merged as fb5051f1e67383a98cf36b21f7cf78a9a44e6301 so it would need to contain that commit.

Comment 5 by ssid@chromium.org, Apr 28 2017

Status: Fixed (was: Untriaged)
Okay Thanks for the info. I will file another bug in case i see more issues.
►

Sign in to add a comment