Crome --enable-precise-memory-info doesn't work and performance.memory is still bucketized
Reported by
012alex...@gmail.com,
Sep 17 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: The problem description with all the steps and screen-shots can be found here: https://stackoverflow.com/questions/46264685/crome-enable-precise-memory-info-doesnt-work-and-performance-memory-is-still 1. Following Chromium Command Line Switches Documentation I ran Chrome with --enable-precise-memory-info flag 2. Then in the opened Chrome instance I tried to check value of window.performance.memory.usedJSHeapSize 3. I execute th following code in console to use more memory: for(let i=0;i<100000;i++) {a.push('sdftgkljhghertyukytedtreut56ytirty7uikty' +i)} 4. looks like inspite of --enable-precise-memory-info flag this info is still bucketized - the value of window.performance.memory stays the same. 5. 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)} What is the expected behavior? I expect window.performance.memory value to change after each execution of: for(let i=0;i<100000;i++) {a.push('sdftgkljhghertyukytedtreut56ytirty7uikty' +i)} What went wrong? The value of window.performance.memory stays the same, while Chrome Task Manager indicates memory usage growth Did this work before? N/A Chrome version: 60.0.3112.113 Channel: n/a OS Version: 10.0 Flash Version:
,
Sep 17 2017
Do you launch new instance of Chrome with `--enable-precise-memory-info` flag when an instance of Chrome is open?
,
Sep 18 2017
I closed all the instances and even checked in Task Manager that there is no any Chrome process running. But I still see the same behavior.
,
Sep 18 2017
,
Sep 19 2017
Tested the issue on windows 10 & 7 using latest stable M61 #61.0.3163.91 and M63 #63.0.3218.0 and followed the steps mentioned in comment #0.: In step 3 , after executing the command , error msg is seen ... attached screencast for reference. @012alex012-- Could you please try in latest stable and if you can still sble to repro the issue , please help us in reproducing the issue on checking the attached screencast. Thanks!
,
Sep 19 2017
hdodda@, please define 'a=[];' in the console before executing step #3.
,
Sep 19 2017
You should first to initiate a by: `var a=[]` (please check the link to the StackOverflow I've published when opened the issue). Otherwise a === undefined.
,
Sep 19 2017
On same computer I've install an additional version of Chrome (this time Dev). It perfectly works in the new version, but still doesn't work in the previous one. I am attaching screen-shots from these test I did right now.
,
Sep 19 2017
Looks like the "problematic" version just allocates a lot of memory as usedJSHeapSize in advance.
,
Sep 19 2017
Any chance `--enable-precise-memory-info` flag works only for Chrome with Dev Channel? I can't anything saying that in the documentation I used: https://peter.sh/experiments/chromium-command-line-switches/ But maybe it's needed just like `processes` permission in extensions can be applied only for Chrome with Dev Channel. This permission (`processes`) is needed in extension to be able to add listener onUpdatedWithMemory (chrome.processes.onUpdatedWithMemory.addListener).
,
Sep 20 2017
Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #60.0.3112.113, latest stable #61.0.3163.91, latest dev #63.0.3218.0 and latest canary #63.0.3219.0. Attached a screen shots for reference. Following are the steps followed to reproduce the issue. ------------ 1. Launched chrome with flag --enable-precise-memory-info. 2. Opened dev tools console and ran command window.performance.memory.usedJSHeapSize (as per comment #8) 3. Observed that usedJSHeapSize value changed every time and Chrome Task Manager also indicated less memory usage growth. Reporter@ - Could you please check this issue on latest stable #61.0.3163.91 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Removing the Needs-Bisect label as of now as it doesn't seems to be reproducible from TE-end. Please feel free to add the same if reproducible. Thanks...!!
,
Oct 3 2017
Marking WontFix based on #11. Please comment if the issue persists in Canary.
,
Oct 3 2017
BTW the memory value updates in 20min intervals, not immediately. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dtapu...@chromium.org
, Sep 17 2017