New issue
Advanced search Search tips

Issue 828513 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

1.3%-3.7% regression in xr.browsing.static at 547426:547437

Project Member Reported by bsheedy@google.com, Apr 3 2018

Issue description

https://chromium-review.googlesource.com/985933 resulted in a fairly small (~24KB) increase in V8 memory usage during VR browsing tests. Considering the size of the regression and that the culprit CL ships a new library, this seems expected to me. ricea@, is this the case?
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=828513

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


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

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

Comment 3 by ricea@chromium.org, Apr 4 2018

Cc: ricea@chromium.org jgruber@google.com yhirano@chromium.org brucedaw...@chromium.org
 Issue 828313  has been merged into this issue.

Comment 4 by ricea@chromium.org, Apr 4 2018

Issue 828311 has been merged into this issue.

Comment 5 by ricea@chromium.org, Apr 4 2018

Components: Blink>Network>StreamsAPI
bsheedy: Yes. This happens every time we change something in the Streams implementation.
 Issue 828788  has been merged into this issue.

Comment 7 by ericde@google.com, May 18 2018

Labels: -M-67 FoundIn-67
Status: WontFix (was: Assigned)
Closing this off as the owners have indicated the size change is expected.
Components: Internals>XR

Sign in to add a comment