New issue
Advanced search Search tips

Issue 865535 link

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



Sign in to add a comment

12.3%-21.8% regression in xr.browsing.static at 574162:574392

Project Member Reported by bsheedy@google.com, Jul 19 
Surprise! Bisect points to https://chromium-review.googlesource.com/1132315.

Due to Issue 865533, I'm not sure whether this has recovered after the revert/reland of the offending patch.
Project Member

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

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

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


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

pixel_2_xl

Comment 2 by bsheedy@chromium.org, Jul 19

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

Comment 3 by mthiesse@chromium.org, Jul 19 

Booooooooooooooooooooooooooooooooooooooooooooo

I think it's impossible that my CL *actually* had a large impact on GPU memory.

Maybe we should de-dup against the other racy memory issues.

Comment 4 by mthiesse@chromium.org, Jul 20

Labels: Target-70

Comment 5 by mthiesse@chromium.org, Jul 20

Labels: -M-69

Comment 6 by mthiesse@chromium.org, Nov 7

Owner: ----
Status: Available (was: Assigned)

Comment 7 by bsheedy@chromium.org, Nov 20

Status: WontFix (was: Available)
►

Sign in to add a comment