New issue
Advanced search Search tips

Issue 913497 link

Starred by 2 users
Status: Fixed
Owner:
oysteine@google.com
Closed: Dec 10
Cc:
npm@chromium.org
oysteine@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.6% regression in rendering.mobile/tasks_per_frame_total_all at 604455:604528

Project Member Reported by npm@chromium.org, Dec 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 10 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=913497

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


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

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 10

Cc: oysteine@google.com
Owner: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15cc9de8140000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
tasks_per_frame_total_all: 47.37 → 56.91 (+9.544)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by oysteine@chromium.org, Dec 10

Status: Fixed (was: Assigned)
Fixed in crrev.com/614540 (graph returning to normal)
►

Sign in to add a comment