Chrome --enable-precise-memory-info doesn't work and performance.memory is still bucketized

Viewed 4161

I have to test memory usage of some pages in Chrome on Windows programmatically.

Here is my Chrome version (60.0.3112.113 - Official Build - 64-bit) enter image description here

Following Chromium Command Line Switches Documentation I ran Chrome with --enable-precise-memory-info flag:

enter image description here

Then in the opened Chrome instance I tried to check value of window.performance.memory.usedJSHeapSize

but looks like inspite of --enable-precise-memory-info flag this info is still bucketized.

enter image description here

even in Chrome Task Manager (Shift + Esc) I see that memory usage is grows up by about 1 Mb after each execution of:

for(let i=0;i<100000;i++) {a.push('sdftgkljhghertyukytedtreut56ytirty7uikty' +i)}

I found only one outdated discussion concerning this issue even if the issue exists I would expect to find more discussions online.

If I do something wrong - what is my mistake?

If this flag is not supported anymore then what is the new correct way to do it?

Thank you!

3 Answers

maybe you need to close all opened chrome window (cmd + q) before run /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-precise-memory-info

Related