New issue
Advanced search Search tips

Issue 826050 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

1.8% regression in xr.browsing.wpr.static at 544649:544664

Project Member Reported by bsheedy@google.com, Mar 26 2018 
The V8 roll at https://chromium-review.googlesource.com/c/chromium/src/+/972861 caused a small increase in V8 peak memory and allocated_by_malloc. This was minor enough that it got lost in the noise of the non-VR memory.top_10_mobile benchmark that measures the same thing on the same pages.
Project Member

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

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

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


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

pixel_xl

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

Components: Internals>VR
Labels: Proj-VR VR-Perf
Status: WontFix (was: Untriaged)
Closing since this isn't VR-specific, and minor enough that the normal memory tests didn't pick it up.

Comment 3 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment