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

Issue 868370 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.6%-12.7% regression in rendering.mobile at 576802:577094

Project Member Reported by pmeenan@chromium.org, Jul 27

Issue description

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

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


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

android-nexus5x-perf
Cc: uwyiming@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1544f2fda40000

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
28.61 → 32.26 (+3.657)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: -pmeenan@chromium.org
Owner: uwyiming@chromium.org
Reverted responsible change in https://chromium-review.googlesource.com/c/chromium/src/+/1153594. If the fix is effective, we should resolve this bug as a dupe of   bug 866981  .

Sign in to add a comment