diff options
| author | Leon Scroggins III <scroggo@google.com> | 2020-11-20 12:23:27 -0500 |
|---|---|---|
| committer | Leon Scroggins <scroggo@google.com> | 2021-03-24 13:25:06 +0000 |
| commit | 368a7a51c652fe39a130ec6f09315df4f7260e53 (patch) | |
| tree | c1f5e2e3e7bd37856a80ef16725622ab156f1002 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 99abec3d81c873621cc174ff9d2132749887b620 (diff) | |
ImageDecoder: use kYes_ZeroInitialized memory
Bug: 183115528
Test: (A)ImageDecoderTest(s) (verify correctness)
Test: monitor showmap_pss_bytes dashboards (verify memory impact)
This lets the decoder leave zero initialized memory untouched. An
Android feature makes untouched zero initialized memory cheaper, and
BitmapFactory takes advantage of it. Do the same for ImageDecoder.
This feature was originally brought up in b/10016979. ImageDecoder saved
memory in other ways, and as I understand it, Android has shifted
towards using (Animated)VectorDrawables. Both of these may have
contributed to us not noticing when we switched from BitmapFactory to
ImageDecoder.
Change-Id: Iecfd1bbfdcc38e1f0bf380b4f4ea5b861cfcf08a
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions