New issue
Advanced search Search tips

Issue 876098 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 28
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

212.9% regression in rendering.desktop at 583894:583969

Project Member Reported by hjd@google.com, Aug 20

Issue description

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

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


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

Win 7 Perf
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/15c251b2640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Cc: enne@chromium.org
Owner: enne@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12dc3ea9640000

cc: Finish frame early if main thread is idle regardless of redraw state by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/430c8fbe06f29f492df7f212a9cc83d272d7634b
16.43 → 16.66 (+0.2223)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Fixed (was: Assigned)
Reverted.

Sign in to add a comment