New issue
Advanced search Search tips

Issue 838602 link

Starred by 1 user
Status: WontFix
Owner:
mthiesse@chromium.org
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

22.6%-40.1% regression in xr.webvr.static at 552196:552246

Project Member Reported by bsheedy@google.com, May 1 2018 
Bisect points to https://chromium-review.googlesource.com/1017589 as the culprit. The memory usage did go back down to about the halfway point between the original and regressed values, but a ~45 MB increase still seems like quite a lot.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 1 2018 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=838602

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3b01e45c8b5b525c1be059735dd8471adc7c0f08c60adc790e4b61d1394a35a7


Bot(s) for this bug's original alert(s):

pixel_xl

Comment 2 by bsheedy@chromium.org, May 1 2018

Components: Internals>VR
Labels: Proj-VR VR-Perf

Comment 3 by mthiesse@chromium.org, May 1 2018 

A memory increase was definitely expected, I don't know how much is or isn't acceptable, but it looks proportional to the size of the buffers.

Maybe we should detect low memory situations and toggle off the quad buffer or something...

Comment 4 by mthiesse@chromium.org, May 1 2018

Status: WontFix (was: Assigned)
Filed issue 838622.

Comment 5 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment