Geek Answers Handbook

Android 5.0 does not support BitmapFactory. Options inPurgeable

I am learning frescolib Facebook. I see that saving the bitmap on ashmemwith the option is inPurgeableso great. We care about memory management, but reduce OutOfMemoryErrorby Davilk heap. I wonder why Android 5.0 is not constantly supported BitmapFactory.Options inPurgeable.
Are there any changes to ART?
Can someone explain the reason for me? Thanks in advance.

EDIT
According to Ed George's answer:
 Why are Facebook engineers still using inPurgeable with Android 3.0 → 4.4?
Do they compile Dalvik heap allocations for predictable performance?

+4
source share
2 answers

This was answered by Fresco blog post . See the section on “Clean bitmaps” and “Having our cake and food”. If you use Fresco, you will get better performance and less OOM, and you will not lose performance predictability.

Please note, although Fresco also faces many challenges for managing raster memory, being very careful to avoid memory leaks and close bitmaps as soon as possible. If you tried to use NDK yourself, instead of using Fresco, you need to be equally careful.

Google , Fresco, Android API, . , Android 5.0 , , . , , , . , , , .

+3

:

API 21. LOLLIPOP . KITKAT , true, , . , (, , getPixels() ), .

, , , :

inPurgeable Dalvik ( API 11), , , , . inPurgeable . Dalvik heap allocations inBitmap.

+2

More articles:


All Articles