VrCore 1.10 increases effective malloc size by ~25% |
||||
Issue descriptionThis is the Chromium-side bug that corresponds to b/67711355 Upgrading to VrCore 1.10 for tests caused a ~25% (~10MB) increase in the memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg metric across all pages in the WebVR Telemetry tests. Example chart: https://chromeperf.appspot.com/report?sid=8db822b23f16362d1ba18e169ca7a8c9677ae92c758c09b51fa8d49c55af2bf1&rev=507813 This memory increase only affects VR usage - the same metric on non-VR Telemetry tests isn't showing an increase.
,
Oct 27 2017
bsheedy is collecting data.
,
Oct 30 2017
Update on this: I got Chrome heap dumps with ToT VrCore and a known good VrCore. I've posted them on b/67711355. krzysio@ has determined the cause general (the sensor stack is allocating way more memory than before), but the root cause hasn't been identified yet AFAIK.
,
Oct 31 2017
Root cause has been found, fix planned to go into VrCore 1.12 (1.11? The next major release I believe)
,
Nov 8 2017
The fix for this has gone into VrCore, and should be available in the next release. I verified that it reduces the memory usage back to normal locally.
,
Jul 4
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ddorwin@chromium.org
, Oct 11 2017Labels: -Pri-2 -Proj-VR M-64 Proj-VR-Daydream Pri-1