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

Issue 713043 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

High memory usage in Youtube automatic player

Reported by land...@opera.com, Apr 19 2017

Issue description

Chrome Version: content_shell (commit 9f01b1a8c8342b49b40ca21ebeb111465793c03f)
OS: Linux Ubuntu 16.04 x86_64

What steps will reproduce the problem?
(1) load https://www.youtube.com/tv?loader=setshi in content_shell
(2) Wait ~27h for memory buildup. Shorter for a smaller buildup.

What is the expected result?
No buildup in live v8 objects and less overall memory usage in renderer.

What happens instead?
After ~27h renderer used ~2G memory.

We have done some internal testing and parts of it looks like a buildup in the oilpan heap which is improved if trace wrappers are disabled. We have done most testing on older versions so see this as a hint more than hard facts. :)
 

Comment 1 by habl...@google.com, Apr 19 2017

Cc: haraken@chromium.org
Components: Blink>MemoryAllocator>GarbageCollection
Labels: -Pri-3 Pri-2
Status: Available (was: Untriaged)

Comment 2 by tasak@google.com, Apr 24 2017

I measured https://www.youtube.com/tv?loader=setshi memory usage by using memory-infra: 
https://docs.google.com/spreadsheets/d/1WKroY_XeiHym79_rrkBUvF_VRbZ3mEiU4tDhjRkjHRQ/edit#gid=817026215

- Total allocated memory ~1.2GB
  - cc/unlocked ~500MB
  - partition_alloc ~300MB
    (ArrayBufferContents ~260MB)
  - v8 ~166MB
  - blink_gc ~16MB(allocated) + ~13MB(freed)

Regarding partition_alloc: It's slowly growing. Maybe are ArrayBuffers leaking? (I suspect that YouTube's script is holding references to the ArrayBuffers somehow.)

Regarding CC: It's big but is only because you're playing YouTube on a foreground tab, right? i.e., the CC will be gone once you send the tab to background, right?


Comment 4 by cbruni@chromium.org, Jul 10 2017

Status: WontFix (was: Available)
This must have been fixed in the mean time, no memory leaks in 61.0.3150.0 when running in several windows over the weekend.

Sign in to add a comment