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

Issue 868344 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 31
Cc:
█ pmeenan@chromium.org
uwyiming@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-20.3% regression in rendering.mobile at 576494:577727

Project Member Reported by pmeenan@chromium.org, Jul 27 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 27 

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

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


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

Android Nexus5 Perf

Comment 3 by pmeenan@chromium.org, Jul 31

Status: WontFix (was: Untriaged)
Recovered
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 2

Cc: uwyiming@google.com
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1644f2fda40000

Add a universal wait-for-page-ready heuristic to the Autofill Captured Sites Interactive Uitest. by uwyiming@google.com
https://chromium.googlesource.com/chromium/src/+/dd60b0b2896699f093771630d10c184e50279b94
36.12 → 39.53 (+3.413)

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

Sign in to add a comment