New issue
Advanced search Search tips

Issue 734147 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
etienneb@chromium.org
tasak@google.com
keishi@chromium.org
erikc...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

2GB facebook renderer: huge BlinkGC and V8

Project Member Reported by ssid@chromium.org, Jun 16 2017 
I see multiple problems with the renderer memory trace.

Attached trace file and V8 heap snapshot.

The Blink GC is 550 MB, out of which only 350MB is live objects. 100 MB is not even allocated and 100MB is free objects.

I can't read anything from V8 snapshot and the heap profiling is not native and doesn't show much information on why 350MB is used in BlinkGC.

V8 snapshot:
https://drive.google.com/open?id=0B7f4beGia2iHRGc3cWJpejRrcmc

Trace with pseudo stack:
https://drive.google.com/open?id=0B7f4beGia2iHc0EtTHVFMXVjcEU

Comment 1 by keishi@chromium.org, Jun 19 2017

Cc: tasak@google.com
The BlinkGC heap utilization of 350/550MB looks normal to me (typical amount of fragmentation for allocation heavy app).

When looking inside BlinkGC, 69MB is Nodes and 199MB is some mystery object. This mystery object is allocated from a JS timer and there are 2 million instances.

V8 heap snapshot doesn't show 2 million Blink side objects so these objects do not have a V8 wrapper. Heap snapshot does show 400MB being used by Object and 181MB used by Array.

In conclusion I don't see anything to support a Blink side leak. It still could be a blink side leak but it could just be JS induced bloat.

Comment 2 by etienneb@chromium.org, Jun 19 2017 

Here are the pseudo-stack allocating objects.
There is more than 1M objects.... this is insane.

The attached files are only for the facebook renderer.
Similar stackframe are observed for other tabs.
malloc.png
33.3 KB View Download
blink.png
31.4 KB View Download
partition.png
25.0 KB View Download

Comment 3 by etienneb@chromium.org, Jun 19 2017

metric.png
9.8 KB View Download

Comment 4 by etienneb@chromium.org, Jun 19 2017 

Trace information
  product-version: "Chrome/60.0.3112.20"
  physical-memory: 64351
  CPU: Linux x86_64

Comment 5 by tasak@google.com, Jun 20 2017 

Would you tell me how to obtain the trace file?
So is it ok to just open www.facebook.com, wait some minutes, and run chrome://tracing?

Comment 6 by ssid@chromium.org, Jun 20 2017 

My trace was taken after a week of leaving facebook tab open on my Linux desktop.

Comment 7 by erikc...@chromium.org, Jun 20 2017

Labels: Needs-Investigation
Status: Available (was: Untriaged)
Keeping Pri-3 because we don't have easy repro steps.
Project Member

Comment 8 by sheriffbot@chromium.org, Jun 21 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment