Issue metadata
Sign in to add a comment
|
navigator.deviceMemory returns wrong value for devices with over 8gb ram
Reported by
ahsaneja...@gmail.com,
May 17 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Steps to reproduce the problem: 1. Get a PC with higher than 8 gigs of ram 2. Run Chrome 3. open console and write "navigator.deviceMemory" What is the expected behavior? The device memory returned is 16GB What went wrong? The device memory returned is 8GB Did this work before? No Does this work in other browsers? N/A Chrome version: 66.0.3359.181 (Official Build) (64-bit) (cohort: Stable) Channel: stable OS Version: 10 Flash Version:
,
May 18 2018
Able to reproduce this issue on Windows 10, Mac OS 10.13.3 on the latest Canary 68.0.3433.0 and latest Stable 66.0.3359.181 as per the original comment. Unable to test the issue on Ubuntu 14.04 and 17.10, as PC with higher than 8GB RAM is not available. Note: Can observe the good behavior till 63.0.3212.0 build and from 63.0.3213.0 build, on running navigator.deviceMemory in console, can see the output as 'undefined'. Hence considered 63.0.3213.0 as bad build. On the latest Canary and Stable, can see the output on Console as 8. Attached are the screen shots for reference. Bisect Information: =================== Good Build: 63.0.3212.0 Bad Build : 63.0.3213.0 By running the per-revision bisect script, below is the Changelog URL. https://chromium.googlesource.com/chromium/src/+log/d3c837936aa0bed3e7e522fe0f515db80c46835f..7bacf86ba10a26e119006365a040a1aa5ea579c3 From the above Changelog, suspecting the below change: Reviewed-on: https://chromium-review.googlesource.com/660481 fmeawad@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Thanks
,
May 18 2018
The issue as originally reported is WAI, we added an upper bound to the reported values at 8 GB for security reasons. In the spec, the full list of possible values: https://w3c.github.io/device-memory/#examples And the reasoninng for upper bounding the value is also in the spec: https://w3c.github.io/device-memory/#sec-security-considerations In general, the value is intended to give an indication of the device class, and at the moment devices with 8+GB of memory should be considered in the same class. The upper bound can change in the future if the commodity hardware available memory shifts upwards. The bisect results are unrelated to this issue, the bisect is showing a revert to postpone adding the feature until it was approved, but it has since re-landed: https://chromium-review.googlesource.com/c/chromium/src/+/716916
,
May 18 2018
You can also check this blog for more how to use details: https://developers.google.com/web/updates/2017/12/device-memory |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, May 18 2018