New issue
Advanced search Search tips

Issue 859587 link

Starred by 2 users
Status: WontFix
Owner:
e...@chromium.org
Closed: Jul 3
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

1%-3.5% regression in xr.browsing.wpr.static at 571216:571313

Project Member Reported by bsheedy@google.com, Jul 2 
Bisect points to https://chromium-review.googlesource.com/1092013. This is a fairly small increase, though, so since it apparently speeds up line-layout so much, it's probably worth eating the cost.
Project Member

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

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

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


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

pixel_2_xl
pixel_xl

Comment 2 by bsheedy@chromium.org, Jul 2

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

Comment 3 by e...@chromium.org, Jul 3

Status: WontFix (was: Assigned)
The increase in memory is only for tests and when LayoutNG is enabled (disabled by default). This should have no effect for the shipping browser as the code path in question is never reached.
►

Sign in to add a comment