New issue
Advanced search Search tips

Issue 836439 link

Starred by 3 users
Status: Duplicate
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

1.6%-97.2% regression in xr.browsing.wpr.static at 550969:551060

Project Member Reported by bsheedy@google.com, Apr 24 2018 
I've tried three separate bisects for this (with the number of attempts before marking a revision good set to 3) and gotten three separate culprit CLs, none of which look like they could have caused memory regressions like this.

Judging by the graph history, this might just be more flakiness?
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 24 2018 

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Apr 24 2018

Components: Internals>VR
Labels: Proj-VR VR-Perf
Status: Available (was: Untriaged)

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

Mergedinto: 842160
Status: Duplicate (was: Available)
From the graphs this just looks like flakiness that first showed up with issue 842160.

Comment 4 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment