New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 901358 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 888558
Owner:
Closed: Nov 2
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6%-∞% regression in avg_surface_fps,frame_times,percentage_smooth,tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 603899:604528

Project Member Reported by 42576172...@developer.gserviceaccount.com, Nov 2

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
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/13f594a1e40000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
thread_raster_cpu_time_per_frame: 0 → 0.02602 (+0.02602)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 888558
Status: Duplicate (was: Assigned)
Cc: alexclarke@chromium.org asamidoi@google.com donna...@intel.com reillyg@chromium.org
 Issue 903176  has been merged into this issue.

Sign in to add a comment