New issue
Advanced search Search tips

Issue 900011 link

Starred by 1 user
Status: Duplicate
Merged: issue 899002
Owner:
backer@chromium.org
Closed: Oct 30
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

1.6%-856.6% regression in xr.browsing.wpr.static at 600168:600676

Project Member Reported by bsheedy@google.com, Oct 29 
Bisect points to https://chromium-review.googlesource.com/c/chromium/src/+/1284435 as the culprit.

My guess is that this is a change in how/when the memory gets measured rather than an actual regression, but WDYT?
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 29 

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

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


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

pixel_2_xl
pixel_xl

Comment 2 by bsheedy@chromium.org, Oct 29

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

Comment 3 by backer@chromium.org, Oct 30

Mergedinto: 899002
Status: Duplicate (was: Assigned)
I believe this is a duplicate. The fix is in the CQ.
►

Sign in to add a comment