New issue
Advanced search Search tips

Issue 876844 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 876473
Owner:
Closed: Aug 27
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3% regression in rendering.mobile at 584567:584585

Project Member Reported by majidvp@chromium.org, Aug 22

Issue description

It is a amall regression and all other tests in the same benchmark has improved significantly at the same time so it seems to be an overall improvement. 

Most likely we can close this as WONTFIX but it is a good idea to see if we can identify the root cause to be sure.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=876844

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


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

Android Nexus5 Perf
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12b45ece640000
Kicked off bisect with wider range
Cc: khushals...@chromium.org
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11ef31d9640000

blink/canvas: Ensure constant PaintImage::ContentId for canvas snapshots. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/f93f8b7c3d3080586deba2a1a7f6b47bcfc4e340
53.76 → 54.86 (+1.105)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 876473
Status: Duplicate (was: Assigned)

Sign in to add a comment