New issue
Advanced search Search tips

Issue 836974 link

Starred by 1 user
Status: WontFix
Owner:
mthiesse@chromium.org
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

1%-4.3% regression in xr.browsing.wpr.static at 552879:552981

Project Member Reported by bsheedy@google.com, Apr 25 2018 
It's time for another case of "memory regressions that make 0 sense". Culprit CL is https://chromium-review.googlesource.com/1024881.

There were a number of GPU memory improvements, which is expected, but I have no idea how Java heap usage went up.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 25 2018 

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Apr 25 2018

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

Comment 3 by mthiesse@chromium.org, Apr 25 2018 

That regression really looks like it's within the noise level of that graph...

It could also be something silly like adding an additional boolean meant java had to allocate an extra block of memory or something - I have no idea how allocation works in java and am really just wildly guessing here.

I'd be inclined to wontFix this one, even if it is a real regression there's nothing I can do about it, and it's a small one.

Comment 4 by bsheedy@chromium.org, Apr 25 2018

Status: WontFix (was: Assigned)
It looks like it's within the noise level in some graphs, but others it's more noticeable. However, I agree that closing as WontFix is fine.

Comment 5 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment