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

Issue 903137 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 904996
Owner:
Closed: Nov 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-3.4% regression in system_health.memory_mobile at 604118:604186

Project Member Reported by alexclarke@chromium.org, Nov 8

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
android-nexus5x-perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: ericrk@chromium.org
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11e2507de40000

EnableGpuRasterizationViewportRestriction bot config by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/924edd7aee62613bf0d3f51b4c4d00e63f5c104e
memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size: 8.014e+07 → 8.249e+07 (+2.356e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 904996
Status: Duplicate (was: Assigned)

Sign in to add a comment