Issue metadata
Sign in to add a comment
|
Vr JavaScript Dialog-induced GPU memory regression |
||||||||||||||||||||||
Issue descriptionA very large 603.0MB (153.6%) increase in GPU memory occurred in the xr.webvr.static benchmark in the revision range 534207 - 534254 (f085668f7e6ce2b5e10310a37d986bb80b365d3d - 9e7ccfa5678bd4f7e12b46b1480f8b924360fb47). Looking at the graph, it looks more likely that the regression actually occurred in the revision range 534063 - 534130 (4af20f07ce09da167dd5631e095483514b5e588b - 147cb419ee7e7a42eb2c5eb7310c5374fdb6d42f). Affected graphs are available at https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQtJ7HhQgM This regression was fixed by the time it was triaged, and seems to have been fixed by a follow-up fix to the VR JavaScript dialog patch.
,
Feb 23 2018
,
Jul 4
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bsheedy@chromium.org
, Feb 22 2018