Issue metadata
Sign in to add a comment
|
52 kb regression in resource_sizes (MonochromePublic.apk) at 495230:495230 |
||||||||||||||||||||
Issue descriptionCaused by “Use SkCodec internally in GIFImageDecoder” Commit: 4fed3346549a90c0de40c02f6388e19e8151e92a Link to size graph: https://chromeperf.appspot.com/report?sid=a097e74b1aa288511afb4cb616efe0f95ba4d347ad61d5e835072f23450938ba&num_points=10&rev=495230 Debugging size regressions is documented at: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase Based on the graph: All growth from native code.
,
Aug 17 2017
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!
,
Aug 17 2017
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 |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 17 2017