New issue
Advanced search Search tips

Issue 756651 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

52 kb regression in resource_sizes (MonochromePublic.apk) at 495230:495230

Project Member Reported by estevenson@chromium.org, Aug 17 2017

Issue description

Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 17 2017

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

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


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

Android Builder
Labels: OS-Android
Owner: cblume@chromium.org
Status: Assigned (was: Untriaged)
See attached diff for more info.

The CL was big but it's not clear to me whether or not this increase was expected. Please have a look and either:

1) Close as “Won't Fix” with a short justification, or
2) Land a fix-up

Thanks!
diff_results.txt
78.8 KB View Download

Comment 3 by cblume@chromium.org, Aug 17 2017

Status: WontFix (was: Assigned)
This is expected and temporary. (Although, not a fast temporary.)

We are consolidating our image decoders into Skia. The patch I landed only moved from our gif decoder into Skia's gif decoder.

The problem is Skia's decoders have some inter-dependence. So until all of the Blink decoders have moved over to Skia's decoders, it will end up taking more binary size. That is the not-a-fast-temporary I mentioned. But eventually, we will have moved all of the image decoders over and the size should bump back down.

Sign in to add a comment