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

Issue 726105 link

Starred by 1 user
Status: WontFix
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: Jun 2017
Cc:
█ junov@chromium.org
█ hpayer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

CBS News page renderer address space grows to over 1GB in ~1 min

Project Member Reported by shrike@chromium.org, May 24 2017 
Chrome Version: 60.0.3091.0
OS: macOS 10.12

What steps will reproduce the problem?
(1) Navigate to http://philadelphia.cbslocal.com/2017/03/10/nope-chrome-extension-lets-you-fend-off-annoying-co-workers-with-class/

What is the expected result?
Reasonable memory usage reported in the Task Manager.

What happens instead?
The renderer quickly grows to over 1GB of address space, with private memory allocations nearly as large.

There is repeating network activity after some 10s of seconds, and that seems to drive the huge increases in memory usage.
trace_cbsphilly-memory-trace.json.gz
19.6 MB Download

Comment 1 by junov@chromium.org, May 25 2017 

The massive memory consumption is mostly on the JavaScript heap. I captured a memory profile, and vpaid.js is definitely an allocation hotspot. It is hard decipher the minified code, but it looks like this script is collecting bids from a very large number of ad networks.

@shrike: why do you think this is a bug in Chrome?

In Firefox, the the memory usage does not skyrocket, but that is only because vpaid.js is aborting due to syntax errors, and the ads on the page are broken.

To me this just looks like a poor quality web site.

Comment 2 by junov@chromium.org, May 25 2017

Cc: junov@chromium.org
Status: WontFix (was: Untriaged)

Comment 3 by shrike@chromium.org, May 25 2017 

> @shrike: why do you think this is a bug in Chrome?

I was hoping someone on the blink/v8 side, with more understanding of how things work, could take a look and assess if it's a Chrome bug or not.

Comment 4 by junov@chromium.org, May 25 2017

Components: -Blink Blink>JavaScript
Status: Untriaged (was: WontFix)
Fair enough, re-opening and triaging to the JavaScript component.

Comment 5 by jochen@chromium.org, May 26 2017

Components: -Blink>JavaScript Blink>JavaScript>GC
Owner: hpayer@chromium.org
Status: Assigned (was: Untriaged)

Comment 6 by hpayer@chromium.org, May 29 2017 

Cannot reproduce on Version 60.0.3110.0 (Developer Build) (64-bit)
Have it open now for 30 minutes. Did you navigate or was the tab inactive? #1 points to a website issue, maybe this was fixed by now?

Comment 7 by shrike@chromium.org, May 30 2017 

Thanks for taking a look. I cannot reproduce it now either.

Comment 8 by hpayer@chromium.org, Jun 12 2017

Status: Fixed (was: Assigned)
Closing since it is not reproducible anymore. Please re-open otherwise.

Comment 9 by erikc...@chromium.org, Jul 25 2017

Status: WontFix (was: Fixed)
►

Sign in to add a comment