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

Issue 827152 link

Starred by 3 users
Status: WontFix
Owner:
█ trchen@chromium.org
Last visit > 30 days ago
Closed: Mar 2018
Cc:
█ trchen@chromium.org
pdr@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1% regression in system_health.memory_desktop at 545873:545919

Project Member Reported by kraynov@chromium.org, Mar 29 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 29 2018

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

[Blink] Make PaintLayer::AncestorDependentCompositingInput external again by trchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/28f75e04b5a1091303e3bddd9621ee04df91ac4d

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

Comment 4 by trchen@chromium.org, Mar 29 2018

Status: WontFix (was: Assigned)
It reverts the gain from r542668. Unfortunately we can't earn that memory save without costing CPU. :(

Comment 5 by trchen@chromium.org, Mar 30 2018 

 Issue 827151  has been merged into this issue.

Comment 6 by trchen@chromium.org, Mar 30 2018 

 Issue 827687  has been merged into this issue.
►

Sign in to add a comment