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

Issue 835929 link

Starred by 1 user
Status: WontFix
Owner:
wangxianzhu@chromium.org
Closed: Apr 2018
Cc:
█ trchen@chromium.org
pdr@chromium.org
wangxianzhu@chromium.org
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.1%-291.5% regression in system_health.memory_desktop at 552498:552586

Project Member Reported by mustaq@chromium.org, Apr 23 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-mac11-air
chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
Project Member

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

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

[SPv175] Repaint non-composited layer on layer visibility change by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/371ffcdbb5dca7fb1a0aeb53956905bb1d4f9fc5

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

Comment 4 by wangxianzhu@chromium.org, Apr 23 2018

Status: WontFix (was: Assigned)
The metrics returned to the previous levels before we introduced the bug when enabled SPv175. The decreased memory before the #c3 CL was because of missing rasterization of layers that changed opacity from zero to non-zero.
►

Sign in to add a comment