New issue
Advanced search Search tips

Issue 874879 link

Starred by 1 user
Status: Duplicate
Owner:
ericrk@chromium.org
Closed: Aug 17
Cc:
ericrk@chromium.org
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

32.1% regression in blink_perf.image_decoder at 583098:583171

Project Member Reported by tdres...@chromium.org, Aug 16 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 16 

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

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


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

Win 7 Perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 16

Cc: ericrk@chromium.org
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14f043ca640000

Hold pre-decoded images until use or 250ms rather than 2 frames by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/520ce5d7136360877309b68ab8b43a7d13c84d82
58.59 → No values

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

Comment 4 by ericrk@chromium.org, Aug 17

Mergedinto: 874878
Status: Duplicate (was: Assigned)
►

Sign in to add a comment