New issue
Advanced search Search tips

Issue 901364 link

Starred by 1 user
Status: Duplicate
Merged: issue 888558
Owner:
oysteine@google.com
Closed: Nov 2
Cc:
tdres...@chromium.org
oysteine@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 8.8% regression in rendering.mobile/tasks_per_frame_total_all at 604426:604516

Project Member Reported by tdres...@chromium.org, Nov 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 2 

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 2

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/119be191e40000

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 → 6.476 (+6.476)

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

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

Comment 4 by oysteine@chromium.org, Nov 2

Mergedinto: 888558
Status: Duplicate (was: Assigned)
►

Sign in to add a comment