New issue
Advanced search Search tips

Issue 911129 link

Starred by 1 user
Status: Duplicate
Merged: issue 906540
Owner:
eroman@chromium.org
Closed: Dec 3
Cc:
maxlg@chromium.org
eroman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 84.9% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 612489:612583

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

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

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

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


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

Android Nexus5X WebView Perf

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

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

Cc: eroman@chromium.org
Owner: eroman@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15865260140000

Recognize --proxy-bypass-list from WebView. by eroman@chromium.org
https://chromium.googlesource.com/chromium/src/+/4bc3f6d6ec942c97293e303f469ccdc4bf551fc2
thread_raster_cpu_time_per_frame: No values → 1.733

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

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

Comment 4 by eroman@chromium.org, Dec 3

Mergedinto: 906540
Status: Duplicate (was: Assigned)
The "regression" is working as intended.
The rendering.mobile tests were broken prior to that change.
Once the failure was corrected, they are expected to run more slowly :)
►

Sign in to add a comment