New issue
Advanced search Search tips

Issue 838883 link

Starred by 1 user
Status: Duplicate
Merged: issue 838456
Owner:
wangxianzhu@chromium.org
Closed: May 2018
Cc:
pdr@chromium.org
wangxianzhu@chromium.org
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.3%-120.2% regression in system_health.memory_mobile at 552737:554931

Project Member Reported by 42576172...@developer.gserviceaccount.com, May 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 2 2018 

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

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


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 3 2018

Cc: pdr@chromium.org wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14e43c73c40000

[SPv175+] Don't create a new chunk with different id and the same properties. by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/976fc1e074a07d78fc4ccb3ab2a9fbd20fd9ce69

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

Comment 4 by wangxianzhu@chromium.org, May 3 2018

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

Sign in to add a comment