New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 851210 link

Starred by 3 users
Status: WontFix
Owner:
█ offenwanger@chromium.org
Last visit > 30 days ago
Closed: Aug 24
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

17.6% regression in xr.webxr.static at 563419:563508

Project Member Reported by bsheedy@google.com, Jun 9 2018 
Culprit CL is https://chromium-review.googlesource.com/c/chromium/src/+/1074223. I would expect an increase in memory from this change, but ~15 KB seems like a bit much.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 9 2018 

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Jun 9 2018

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

Comment 3 by btebbs@chromium.org, Jul 4

Components: Internals>XR

Comment 4 by efoo@chromium.org, Aug 7 

Removing Internals>VR component and assigning to Internals>XR

Comment 5 by efoo@chromium.org, Aug 7

Components: -Internals>VR

Comment 6 by offenwanger@chromium.org, Aug 24

Status: WontFix (was: Assigned)
I cannot see anything in the CL that would cause this. I'm going to assume that this is not actually caused by this CL.
►

Sign in to add a comment