setImageResource and memory leak

Question

In my Activity, I use imageView.setImageResource(R.drawable.image_name); about 8 times for different views.

I kept opening and closing the activity repeatedly and I notice the app is getting laggy. I am wondering if this is related to memory leak? Is it because of that piece of code?

now should be the time to start using `MAT` and checking what is still in memory — thepoosh, Jan 27 '16 at 06:45
Totally a opinion based question. What are your findings ? did you use any Memory Analysis tool ? like MAT or so ? how big is your image ? what resolution is your image? how much device memory has ? what is the heap size ? — Murtaza Khursheed Hussain, Jan 27 '16 at 06:48

score 2 · Accepted Answer · answered Jan 27 '16 at 06:44

2

You should recycle() all your bitmaps when done using them. If you want to destroy them when activity is finish()ed, you can override onDestroy to destroy all bitmaps

answered Jan 27 '16 at 06:44

setImageResource is counted as Bitmaps? – JayVDiyk Jan 27 '16 at 06:44
1

It should be of type `BitmapDrawable`. Check this http://stackoverflow.com/a/8306683/4795214 – Jan 27 '16 at 06:45
How do I recycle the bitmap if I use setImageResource in the first place? Thanks – JayVDiyk Jan 27 '16 at 06:46
1

Check this answer http://stackoverflow.com/a/13415604/4795214 – Jan 27 '16 at 06:47

setImageResource and memory leak

1 Answers1