New issue
Advanced search Search tips

Issue 841229 link

Starred by 2 users
Status: WontFix
Owner:
khushals...@chromium.org
Closed: May 2018
Cc:
piman@chromium.org
khushals...@chromium.org
primiano@google.com
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

23.7% regression in system_health.common_mobile at 556100:556168

Project Member Reported by primiano@google.com, May 9 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 9 2018 

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

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


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

android-nexus5
Project Member

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

Cc: chrishtr@chromium.org piman@chromium.org 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/16efa64fc40000

cc: Enable checkerimaging only on developer opt-in. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/465219a86327b393fb6d92e894fd80919f9f9a0a

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

Comment 4 by khushals...@chromium.org, May 17 2018

Status: WontFix (was: Assigned)
So this case actually does have an image that is now decoded on the critical path vs an async decode on a background worker thread earlier, causing the paint to be blocked on the decode. This is expected because the change makes that feature opt-in.
►

Sign in to add a comment