New issue
Advanced search Search tips

Issue 900929 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3% regression in memory.top_10_mobile at 603125:603179

Project Member Reported by hjd@google.com, Nov 1

Issue description

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

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


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

Android Nexus5 Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: bokan@chromium.org
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12df1cc5e40000

Performance fix for top controls-affected raster by bokan@chromium.org
https://chromium.googlesource.com/chromium/src/+/b2d410710e7ea7c5a33798ff6b5d5191b1951b5e
memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size: 6.554e+07 → 6.75e+07 (+1.969e+06)

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

Benchmark documentation link:
  None
Mergedinto: 899005
Status: Duplicate (was: Assigned)
Mergedinto: -899005 900928

Sign in to add a comment