MG
recycling bitmaps where appropriate
Size: a a a
2020 October 06
MG
(such as recycling the current bitmap before setting a new bitmap, and recycling when the bitmap would no longer be used)
MG
during this period, i get a brief spike in memory usage before the GC cleans up my recycled bitmaps and other data
AT
Avoid creating objects in onDraw.
MG
can i create objects in onMeasure?
AT
it will be almost the same
MG
where should i create them?
AT
>3. i then cache the given stream,
Why you caching streams instead of bitmaps itself?
Why you caching streams instead of bitmaps itself?
MG
cus uncompressed bitmaps take up loads of memory
MG
(in my case, 15MB per full screen bitmap)
MG
vs the same bitmap compressed to JPEG (about 200kb)
AT
well then you will have to decompress it every frame. and have problems with gc
MG
onDraw is not being invoked constantly
MG
gtg, dinner
AT
if you need to speedup drawing of scaled image - you can cache big image. then create scaled vadiant each time you need a new scale.
MG
i dont
AT
you can use ScaleDrawable btw ...
AT
just create it once and use in onDraw...
MG
i need to decrease my memory usage during the bitmap loading/drawing of 30+ bitmaps in recycler view
AT
As i remember BitmapFactory.decode* can create sacaled images from file of data without creating big image. do you try this approach ?