New issue
Advanced search Search tips

Issue 862630 link

Starred by 1 user
Status: WontFix
Owner:
khushals...@chromium.org
Closed: Jul 11
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-VR
Proj-XR



Sign in to add a comment

2.5%-11730.4% regression in xr.browsing.wpr.static at 573395:573504

Project Member Reported by bsheedy@google.com, Jul 11 
Bisect points to https://chromium-review.googlesource.com/1123894 as the culprit. Not sure if this is just a biproduct of adding more tracing or a legitimate regression, but increases of up to 27.2 MB seems way too high for just adding tracing.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 11 

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

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


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

pixel_2_xl
pixel_xl

Comment 2 by bsheedy@chromium.org, Jul 11

Components: UI>Browser>VR
Labels: Proj-XR-VR VR-Perf

Comment 3 by khushals...@chromium.org, Jul 11

Status: WontFix (was: Assigned)
This is all completely expected, all regressions are skia size reported by the GPU process, which was missing in the dumps prior to this change. The overall PSS is the same.
►

Sign in to add a comment