New issue
Advanced search Search tips

Issue 824947 link

Starred by 1 user
Status: WontFix
Owner:
danakj@chromium.org
Closed: Mar 2018
Cc:
bsheedy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

1.3%-228168.2% regression in xr.browsing.wpr.static at 544467:544578

Project Member Reported by bsheedy@google.com, Mar 22 2018 
https://chromium-review.googlesource.com/953386 caused a ~2.6 MB increase in a number of memory metrics in VR browsing tests. There's a similar decrease in other memory metrics in the same revision range, so my guess is that this changed just caused memory allocation to shuffle around a bit? If so, just close out as a wontfix.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 22 2018 

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Mar 22 2018

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

Comment 3 by danakj@chromium.org, Mar 22 2018

Status: WontFix (was: Assigned)
Yes it moved allocations to a different label

Comment 4 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment