Glide is not releasing memory when using Databinding rules

Asked Jun 07 '18 at 05:28

Active Jun 07 '18 at 05:28

Viewed 643 times

I'm using fragments in a ViewPager, each page is having imageviews. I'm following databinding rules and i load image using Glide in BindingUtils. Now issue is that when i call Glide.clearMemory() in onDestroyView of fragment. It doesn't clear memory and heap keeps on growing.

BindingUtils:

@BindingAdapter("imageUrl")
    public static void setImageUrl(ImageView imageView, String url) {
        Context context = imageView.getContext();
        if (url != null) {
            Glide.with(context).load(url).load(url))
                    .into(imageView);
   }
    }

From Fragment:

@Override
    public void onDestroyView() {
        if (getContext() != null)
            Glide.get(getContext()).clearMemory();
        super.onDestroyView();
    }

I checked a this answer at stackoverflow, and it states that imageView.getContext(); gives application context and when we release memory from fragment then it has fragment context. So, question is that how can i get the related context and release the memory then? Any ideas would be appreciable.

asked Jun 07 '18 at 05:28

Usman Rana

2,067
1
21
32

hi did you solve the problem ? – Mehmet Gür May 13 '20 at 18:58
1

I had to remove dataBinding in that case. Glide call was sent from the fragment/activity by passing the same context that we use to clear the request. – Usman Rana May 14 '20 at 05:56
So `Glide.get(getContext()).clearMemory();` is not working isn't it? Because I'm also using this exactly but it seem It doesn't reduce memory usage. – Mehmet Gür May 15 '20 at 01:37
1

yes, it didn't see working when i was on that task. – Usman Rana May 15 '20 at 06:35

Glide is not releasing memory when using Databinding rules

0 Answers0