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

Issue 846681 link

Starred by 1 user
Status: Duplicate
Merged: issue 846676
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: May 2018
Cc:
mlippautz@chromium.org
█ hpayer@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.6% regression in v8.browsing_mobile at 558508:558585

Project Member Reported by hpayer@google.com, May 25 2018 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 26 2018

Cc: mlippautz@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1272cd22240000

[oilpan] Cleanup tracing scopes by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/c6ff060cc760c7cb8a44be7314ce5e96757213c6

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by hpayer@chromium.org, May 29 2018

Mergedinto: 846676
Status: Duplicate (was: Assigned)
►

Sign in to add a comment