New issue
Advanced search Search tips

Issue 825599 link

Starred by 2 users
Status: Duplicate
Owner:
agrieve@chromium.org
Closed: Apr 2018
Cc:
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.3% regression in system_health.memory_mobile at 544800:544870

Project Member Reported by sullivan@chromium.org, Mar 25 2018 
Note that several metrics move in the positive direction in the same range: https://chromeperf.appspot.com/group_report?sid=8b18bc7057abdd0ca3919396596e2884c69f531940949d97a27942f12697c393

We should check whether the culprit CL is a net win when it is identified.

This is likely related to  bug 825598
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 25 2018 

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

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


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

android-nexus6

Comment 3 by sullivan@chromium.org, Apr 2 2018

Owner: agrieve@chromium.org
Status: Assigned (was: Untriaged)
agrieve: the pinpoint job is sloooow since we are under-provisioned on N6, but it looks like this is r544837, "Android: Disable obfuscation for org.chromium.content.browser.input". Is this a dupe of bug 825630?

Comment 4 by agrieve@chromium.org, Apr 3 2018

Mergedinto: 825630
Status: Duplicate (was: Assigned)
Yeah, basically any alert with that commit in the range is a dupe (I've had ~10 perf bugs from it so far :/).
►

Sign in to add a comment