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

Issue 832120 link

Starred by 2 users
Status: WontFix
Owner:
█ jamwalla@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
pdr@chromium.org
wangxianzhu@chromium.org
ajuma@chromium.org
boliu@chromium.org
█ eakuefner@chromium.org
█ jamwalla@chromium.org
changwan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.4%-18.2% regression in system_health.memory_mobile at 549350:549435

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 12 2018 

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

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


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

android-nexus5
android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 12 2018

Cc: ajuma@chromium.org jamwalla@chromium.org
Owner: jamwalla@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13beb7fcc40000

UpdateAnimationState(true) if early out due to no damage by jamwalla@chromium.org
https://chromium.googlesource.com/chromium/src/+/34ff3016ce7939730b5c180e3039961e7fe2c592

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 13 2018

Cc: pdr@chromium.org wangxianzhu@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15c40392c40000

[SPv175+] Don't create OverflowClip if contents don't overflow by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/62abeca8161aedf25ee126d4bc63bd3cbeac4085

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

Comment 6 by wangxianzhu@chromium.org, Apr 13 2018 

The 3 alerts are due to different reasons. I just removed the alert in #c5 from this bug and filed  bug 832763  for it.

Comment 7 by wangxianzhu@chromium.org, Apr 13 2018 

Sorry, I made a mistake for  bug 832763 . That alert should belong to this bug. Filed  bug 832769  which contains the correct alerts.

The automatic bisect jobs may merge the new bugs back to this bug. I will separate  bug 832769  again when that happens.

Comment 8 by wangxianzhu@chromium.org, Apr 13 2018 

 Issue 832763  has been merged into this issue.

Comment 10 by jamwalla@chromium.org, Apr 18 2018

Cc: boliu@chromium.org changwan@chromium.org
Status: WontFix (was: Assigned)
This metric went down temporarily after
https://chromium.googlesource.com/chromium/src/+/05381aa3a9570439a16774f120bc3c0d20c9de81
but the culprit CL was a bug fix for that change. This regression says things are back to normal now. I started a bisect of the improvement range to be sure.
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Apr 20 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12ab77b6c40000

WebView: enable cc::switches::kCheckDamageEarly by jamwalla@chromium.org
https://chromium.googlesource.com/chromium/src/+/05381aa3a9570439a16774f120bc3c0d20c9de81

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

Sign in to add a comment