Issue metadata
Sign in to add a comment
|
60KB regression in resource_sizes (MonochromePublic.apk) at 495810:495810 |
||||||||||||||||||||
Issue descriptionCaused by [wrapper-tracing] Enable use of mixins for values Commit: ac528b27b356ecddcf4c400c7de996eefd7f8e38 Link to size graph: https://chromeperf.appspot.com/report?sid=a097e74b1aa288511afb4cb616efe0f95ba4d347ad61d5e835072f23450938ba&num_points=10&rev=495810 Debugging size regressions is documented at: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase The increase consists of 61KB native code. It's not clear to me whether or not this increase was expected. Please have a look and either: Close as “Won't Fix” with a short justification, or Land a revert / fix-up.
,
Aug 21 2017
The increase is expected. Reason: We are adding 1 virtual call back to a sizable amount of objects from which we removed 4 virtual calls a few months ago [1]. It's still better than initially, just not as good anymore. [1] https://codereview.chromium.org/2595053002/ |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 21 2017