Issue metadata
Sign in to add a comment
|
Quantized window.performance.memory
Reported by
victorse...@gmail.com,
Jun 20 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36 Steps to reproduce the problem: 1. Start chrome with --enable-precise-memory-info flag 2. Open a simple demo page that allocate memory (https://github.com/paulirish/memory-stats.js/blob/master/demo/index.html). At the beginning of test, used memory is 9MB and after some time it is updated to 40MB. What is the expected behavior? performance.memory metrics should not be quantized when using --enable-precise-memory-info What went wrong? performance.memory metrics are quantized. Did this work before? N/A Chrome version: 59.0.3071.104 Channel: stable OS Version: 6.3 Flash Version: --enable-precise-memory-info work on a recent build of Chromium (Version 61.0.3133.0 (Developer Build) (32-bit))
,
Jul 17 2017
,
Jul 17 2017
I can spot where this flag is _supposed_ to change the exposed values: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/timing/MemoryInfo.cpp?type=cs&q=f:memoryinfo+precisememoryinfo However, this implementation has been in a poor state of maintenance for a while and is now basically deprecated. See: https://bugs.chromium.org/p/chromium/issues/detail?id=326370#c41 Apologies for not resolving this bug before the new memory API is available, but.. only so many hours in a day. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Jun 29 2017