New issue
Advanced search Search tips

Issue 818686 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2%-24.3% regression in system_health.memory_desktop at 539181:539412

Project Member Reported by rmcilroy@chromium.org, Mar 5 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=818686

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


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

android-nexus7v2
chromium-rel-mac11-pro
chromium-rel-mac12
linux-release
Cc: chrishtr@chromium.org wangxianzhu@chromium.org piman@chromium.org
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/148c1782440000

Revert "[SPv175] Enable SlimmingPaintV175 by default" by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/04aa2e7e64a78efccb25757afcc36e21c5d6ac0c

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Components: Blink>Paint
Labels: SPv175-Progression
Status: WontFix (was: Assigned)
Why aren't the bugs automatically merged?
Please ignore the question in #c4. It's a real question but doesn't apply to this bug.

Sign in to add a comment