New issue
Advanced search Search tips

Issue 871253 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4% regression in system_health.memory_desktop at 579453:579529

Project Member Reported by chiniforooshan@chromium.org, Aug 6

Issue description

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

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


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

Win 7 Nvidia GPU Perf
Cc: ethannicholas@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/169c3c00640000

Re-re-land "added GrSkSLFP and converted DitherEffect to use it" by ethannicholas@google.com
https://skia.googlesource.com/skia/+/0054311bf3b4f619a631e95d8aa1ea2d4bfd01c6
2.616e+07 → 2.641e+07 (+2.489e+05)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment