New issue
Advanced search Search tips

Issue 875340 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 20
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

20.5%-316.4% regression in thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 582172:582191

Project Member Reported by 42576172...@developer.gserviceaccount.com, Aug 17

Issue description

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

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


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

Android Nexus5X WebView Perf
Cc: cduvall@chromium.org
Owner: cduvall@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11d740fa640000

Enable subresource redirects to all schemes with network service by cduvall@chromium.org
https://chromium.googlesource.com/chromium/src/+/b2680c227c2594e12eaab1962fc9d9e350616a19
4.924 → 12.97 (+8.046)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14bc486e640000
Status: Fixed (was: Assigned)
This was fixed by https://chromium-review.googlesource.com/c/chromium/src/+/1178576

Sign in to add a comment