New issue
Advanced search Search tips

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

22.7% regression in blink_perf.layout at 579910:579927

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

Issue description

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

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


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

Android Nexus5X WebView Perf
Cc: rnk@google.com etienneb@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16b3d558640000

Add memory metric to trace event to investigate omnibox performance by etienneb@chromium.org
https://chromium.googlesource.com/chromium/src/+/e1b21dc79f36dc4c7ddcb9ce606b94751eedeeca
1520 → 1532 (+12.07)

Roll clang 337439:338452. by rnk@google.com
https://chromium.googlesource.com/chromium/src/+/cc14e55b5cd9359e09aa9b8aa8795b100031abfb
1529 → 1934 (+405.2)

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