Issue metadata
Sign in to add a comment
|
System UI fix-induced GPU memory regression |
||||||||||||||||||||
Issue descriptionhttps://chromium.googlesource.com/chromium/src/+/57ae8192495092a13d496038dbe71fdfabaab061 seems to be the cause of the 3 GPU memory regressions reported at https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQrKf1vgkM (4.3 MB increase). This might be an unavoidable increase, but if we can reduce it, that would be great.
,
Feb 13 2018
I wish we could somehow know where that extra GPU memory was coming from, because I have literally no idea where to begin on understanding this one. Minor changes to how the activity is launched /shouldn't/ cause GPU memory regressions :P
,
Feb 13 2018
I've gotten heap dumps from Chrome before, but I'm not aware of a good way to get GPU memory usage.
,
Feb 22 2018
,
Jul 4
,
Aug 7
Removing Internals>VR component and assigning to Internals>XR
,
Aug 7
,
Nov 7
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mthiesse@chromium.org
, Feb 13 2018