New issue
Advanced search Search tips

Issue 841414 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 839767
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

39.7% regression in blink_perf.canvas at 555165:556041

Project Member Reported by wangxianzhu@chromium.org, May 9 2018

Issue description

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

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


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

win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 16 2018

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/15f5af3bc40000

blink: Set up a cc::SoftwareImageDecodeCache for canvas image decodes. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/49fc8a9c4a9eb46faa2258daea5bdbee48da7dcb

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

Sign in to add a comment