New issue
Advanced search Search tips

Issue 749479 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
panicker@chromium.org
yoavweiss@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Unable to see impact of 200mb object

Project Member Reported by jakearchibald@chromium.org, Jul 27 2017 
https://cache-memory-test.glitch.me/

Click "cache large resource" then wait for console log.
GC.
Profile & press "get as buffer"

This brings a 200mb into memory, but I can't find anything in devtools that shows this allocation.

Comment 1 by a...@rigo.sk, Jul 27 2017 

My observations:

img1.png: performance.memory information doesn't include the large Uint8Array() allocations on the window object.
img2.png: the Memory timeline doesn't show the allocation event (while the summary table includes it correctly)

The Performance tab should record the allocation event, however it doesn't contain the info.
img1.png
64.0 KB View Download
img2.png
94.8 KB View Download

Comment 2 by dgozman@chromium.org, Jul 27 2017

Owner: alph@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by alph@chromium.org, Jul 27 2017

Components: -Platform>DevTools>Memory Blink>PerformanceAPIs
Owner: ----
Status: Unconfirmed (was: Assigned)
DevTools memory profiler can only profile JS heap memory. Native memory is not instrumented. As long as Uint8Array is a native array it is not instrumented by memory timeline. So the behavior is expected.

Reassigning to performance API folks for performance.memory issue.

Comment 4 by tdres...@chromium.org, Jul 31 2017 

As per crbug.com/709008, in the long term, we want to replace performance.memory with something on the standards track.

I think the reason why this doesn't show up in performance.memory is the same as the response in #3: native memory isn't instrumented.

WontFixing, but we should address this in whatever we decide to replace performance.memory with.

Comment 5 by tdres...@chromium.org, Jul 31 2017

Status: WontFix (was: Unconfirmed)
►

Sign in to add a comment