New issue
Advanced search Search tips

Issue 860294 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 859635
Owner:
Closed: Jul 9
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

72.3% regression in system_health.memory_mobile at 571636:571766

Project Member Reported by hjd@google.com, Jul 4

Issue description

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

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


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

android-nexus5X
Cc: enne@chromium.org
Owner: enne@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c3a522a40000

Turn on OOP Raster on android bots by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/d82c4fabc5cc6cbe6b475186ed9fa0216980e533
1.41e+08 → 2.418e+08 (+1.008e+08)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 859635
Status: Duplicate (was: Assigned)

Sign in to add a comment