VR 2D UI Fallback memory regression |
||||||
Issue descriptionThe 2D UI fallback CL (https://chromium.googlesource.com/chromium/src/+/6396120689bb229328c2f351f44a05de54c40fde) ended up causing a wide range of memory regressions while in VR (see https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQpKn_5AgM). Some of these are minor, and I imagine we're going to have to eat some amount of memory increase, but we need to determine what we can reduce while keeping the same functionality.
,
Feb 22 2018
,
Feb 26 2018
Won't get to this for 66.
,
Mar 2 2018
,
Mar 14 2018
WE're talking about flipping the native ui flag to default on and while I don't love taking a memory hit, I think this can not block unless we see evidence from canary/dev that it's making things really bad
,
Mar 20 2018
The 2D fallback UI is in 66 not behind a flag, so we should have already seen any perf regressions that might have resulted from this (aside from the memory regression). If you look at the linked perf graph, apparently this was fixed by https://chromium.googlesource.com/chromium/src/+/cd1b5ac7506a7403ea69072718b8126b7e80951b
,
Mar 23 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tiborg@chromium.org
, Jan 25 2018Labels: M-66
Owner: mthiesse@chromium.org
Status: Assigned (was: Untriaged)