New issue
Advanced search Search tips

Issue 907101 link

Starred by 1 user
Status: Duplicate
Merged: issue 907092
Owner:
digit@google.com
Closed: Nov 21
Cc:
digit@google.com
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.4%-4.8% regression in memory.top_10_mobile at 609142:609150

Project Member Reported by mustaq@chromium.org, Nov 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 20 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=907101

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


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

Android Nexus5 Perf
android-nexus5x-perf

memory.top_10_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 20

Cc: digit@google.com
Owner: digit@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/149c7700140000

android: build: Enable RELR packed relocations for libchrome.so by digit@google.com
https://chromium.googlesource.com/chromium/src/+/cf14fec1c386dc51a6aec3dcc395f1a3527d71b7
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 9.846e+07 → 1.022e+08 (+3.741e+06)

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

Benchmark documentation link:
  None

Comment 4 by digit@google.com, Nov 21

Mergedinto: 907092
Status: Duplicate (was: Assigned)
►

Sign in to add a comment