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

Issue 903107 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

20.1% regression in system_health.memory_mobile at 600384:600413

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=903107

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


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

Android Nexus5 Perf

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

Bound time to delete cc::Resource by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/9bf42619ce76159d90ab4b968208ad620c042ac2
memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size: 7.859e+07 → 9.24e+07 (+1.381e+07)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 899002
Status: Duplicate (was: Assigned)
This was fixed a while ago and updated graphs show that.

Sign in to add a comment