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

Issue 878814 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

19.5% regression in media.mobile at 585830:586693

Project Member Reported by hubbe@google.com, Aug 29

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=878814

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


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

Android Nexus5 Perf

media.mobile - Benchmark documentation link:
  None
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/13aa6085640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Status: WontFix (was: Assigned)
Cannot reproduce.

Cc: enne@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1353dbd5640000

gpu: disable oop raster on Adreno Lollipop and earlier by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/4b51d24604846cd3d049946e70e9ccb535a4b0c2
5.602e+06 → 6.585e+06 (+9.83e+05)

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

Sign in to add a comment