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

Issue 724122 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome , Mac
Pri: 2
Type: Bug

Blocked on:
issue 738031



Sign in to add a comment

Vice Motherboard is very janky

Project Member Reported by igo@chromium.org, May 18 2017

Issue description


repro:

visit https://motherboard.vice.com/en_us/article/leave-chrome-for-opera

scroll around up and down. make the infinite scroll load.

experience jank.

If you follow task manager, the site quickly eats up 700+MB of RAM

This happens on Chromebooks and Chrome desktop for Macbook Pro.

It also is seen in Safari, perhaps a little less severe (need to test further).
 
Labels: Performance-Responsiveness OS-Mac

Comment 2 by hpayer@chromium.org, May 18 2017

Cc: primiano@chromium.org mlippautz@chromium.org u...@chromium.org bccheng@chromium.org
Owner: jochen@chromium.org
On a first glance, it looks like the webpage is leaking. Scrolling down for a while will continuously increase memory. Hitting the garbage bin in dev tools does not help to clean-up. There are a lot of closures on the JS heap, I also see the botguard script which is a known leak. Overall it looks like a webpage leak. Assigning to the current memory sheriff for further investigation.
Status: Assigned (was: Untriaged)

Comment 4 by jochen@chromium.org, Jun 27 2017

Owner: u...@chromium.org
Passing on to current sherrif

Comment 5 by u...@chromium.org, Jun 29 2017

Blockedon: 738031
I agree with assessment in comment #2. The webpage is leaking. The jank comes from scripting (I attached performance profile). There are JS function calls that take more than 1000 ms.

Garbage collection takes about 20% of that time. This will improve when concurrent marking is implemented ( crbug.com/694255 ). I also noticed that sometimes we do full GC instead of incremental GC. I filed  crbug.com/738031  for this.

Other than that, there is nothing actionable for the garbage collection team.


Profile-20170629T171724.json.tar.gz
5.6 MB Download

Comment 6 by u...@chromium.org, Jun 30 2017

Cc: -igo@chromium.org
Owner: igo@chromium.org
Status: Untriaged (was: Assigned)
I landed a fix for  crbug.com/738031  that replaces full GCs with incremental GCs. That should improve jank slightly.

Since the webpage is leaking memory and most of jank comes from long running JS functions, I think the problem is in webpage code rather than in Chrome.

Assigning back to igo@, to make a call to either close this as "won't fix" or start performance traiging outside GC.

Status: Assigned (was: Untriaged)
igo@, can you check again?

Sign in to add a comment