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

Issue 705425 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
derat@chromium.org
cmumford@chromium.org
teravest@chromium.org
sonnyrao@chromium.org
█ reve...@chromium.org
█ bccheng@chromium.org
semenzato@chromium.org
█ nduca@chromium.org
█ kanliu@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

latimes.com exposes a memory leak in Chrome?

Project Member Reported by puneetster@chromium.org, Mar 27 2017 
Chrome Version       : 58.0.3029.31
OS Version: 9334.18.0
URLs (if applicable) :latimes.com
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Visit latimes.com and scroll around 
2. watch memory usage of renderer using Chrome task manager
3. After a minute or two it will grow to > 1GB.  It keeps going up but not at an exponential rate.

What is the expected result?
I am not expecting it to keep growing and certainly not to a GB


What happens instead of that?
Memory consumption grows to > 1GB

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 9334.18.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.31 Safari/537.36

Comment 1 by derat@chromium.org, Mar 27 2017 

Does the memory consumption go down when you reload the tab? If so, it's a memory leak in latimes.com, not in Chrome.

Comment 2 by laforge@google.com, Mar 27 2017

Owner: rsch...@chromium.org
Status: Assigned (was: Unconfirmed)
Hey Ryan,

Could you help find an owner for this?

Comment 3 by reve...@chromium.org, Mar 27 2017 

Find attached a memory-infra trace from latimes.com after scrolling up/down the page for ~10 min on Kevin device with canary build. I'm not seeing an increase in memory usage on this device and build. It stabilizes around 400MB for latimes.com renderer process and GPU/Browser process doesn't seem to increase either.
trace_latimes-memory-infra.json.gz
2.5 MB Download

Comment 4 by semenzato@chromium.org, Mar 27 2017

Cc: semenzato@chromium.org
Just tried this on my cyan with ToT.  Serious memory leak.  Got to 1GB in a few minutes without any user activity.  Then I interrupted the experiment.

Comment 5 by derat@chromium.org, Mar 27 2017 

Does closing or reloading the tab result in the memory being reclaimed?

Do we have any mitigations against in-page memory leaks?

Comment 6 by bccheng@chromium.org, Mar 28 2017

Cc: nduca@chromium.org
nduca@ just sent this out to a few chrome mailing lists:

https://nelsonslog.wordpress.com/2017/03/25/la-times-and-ads/

Comment 7 by rsch...@chromium.org, Sep 20 2017

Owner: ----
Status: Available (was: Assigned)

Comment 8 by ovanieva@google.com, Feb 9 2018

Components: Internals>Instrumentation>Memory

Comment 9 by primiano@chromium.org, Feb 13 2018

Components: -Internals>Instrumentation>Memory
Labels: Performance-Memory
-Internals>Instrumentation>Memory, that component is only for bugs/feeature in the memory instrumentation code. Use Performance-Memory to put this in the memory triage queue.

Comment 10 by derat@chromium.org, Feb 13 2018

Status: WontFix (was: Available)
WontFixing since #6 seems to explain this.
►

Sign in to add a comment