New issue
Advanced search Search tips

Issue 872124 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

6.4%-69% regression in blink_perf.layout at 579897:579927

Project Member Reported by toyoshim@chromium.org, Aug 8

Issue description

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

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


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

Android Nexus5X WebView Perf
Cc: rnk@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13750d84640000

Roll clang 337439:338452. by rnk@google.com
https://chromium.googlesource.com/chromium/src/+/cc14e55b5cd9359e09aa9b8aa8795b100031abfb
719.1 → 1427 (+707.8)

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