Issue metadata
Sign in to add a comment
|
69.9KiB regression in resource_sizes (MonochromePublic.apk) at 618079:618079 |
||||||||||||||||||||
Issue descriptionCaused by “Build with _LIBCPP_ABI_UNSTABLE” Commit: 0f0b0a857e911b152d694c20852b2424ce7868da Link to size graph: https://chromeperf.appspot.com/report?sid=bb23072657e2d7ca892a1c3fa4643b1ee29b3a0a44d0732adda87168e89c0380&num_points=10&rev=618079 Link to trybot result: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-binary-size/122983 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: entirely native lib size 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. It typically takes about a week of engineering time to reduce binary size by 100kb so we'd really appreciate you taking some time exploring options to address this regression!
,
Dec 20
Assigning to thomasanderson@chromium.org because this is the only CL in range: Build with _LIBCPP_ABI_UNSTABLE BUG= 747676 R=thakis Change-Id: Ib3e8d058b380764ee55de77b5993b3ecbf7137e9 Reviewed-on: https://chromium-review.googlesource.com/c/1379066 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#618079}
,
Dec 20
_LIBCPP_ABI_UNSTABLE adds some more code to c++ templates like vector and string that get instantiated everywhere so I'm not surprised the binary size increased. I think overall it should be worth it given the potential runtime benefits. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 20