Images inside recyclerview flash when notifyDataSetChanged() is called

I’m migrating my code from Picasso to Coil and discovered a strange behaviour non present with Picasso.

A recycler view contains images but when I call notifyDataSetChanged() on the adapter some images flash as shown in attached GIF

I created a project useful to reproduce the bug, CoilFlashing

Version Coil 0.9.4 Android 9 and 10 under Android emulator, Xiaomi MiA1, Pixel 3XL

[colinrtwhite]

@mattlogan I agree this behaviour isn’t best for UX in certain cases. Also after reviewing Picasso’s code, it looks like they do check the memory cache on the main thread. They’re also able to avoid waiting for the request’s size as their Transformation interface does not include a size param (which limits what you can do with a transformation).

Coil clears the drawable in onClear to support bitmap pooling and also to preemptively clear images attached to detached Fragments and detached views in a RecyclerView’s view pool. We could avoid calling onClear if bitmap pooling is disabled, however we still clear the drawable in onStart at the beginning of the next request.

Unfortunately there are two competing use cases with Interceptor support and maximizing UI thread performance on one hand and synchronous memory cache checks on the other. That said, I think it’s worthwhile (and possible) to support both use cases with a boolean flag when constructing your image loader - something like ImageLoader.Builder.allowSynchronousMemoryCacheChecks(true/false). allowSynchronousMemoryCacheChecks would need to be disabled to add an Interceptor. What do you think? I’m going to reopen this issue to track.

[mattlogan]

Hey Colin - I understand your reasoning above for checking the cache asynchronously, but I noticed that Picasso doesn’t have this issue despite also checking the memory cache off the main thread. I’m not sure I understand why checking the memory cache asynchronously necessitates clearing & reloading the image as it appears to be doing now. Perhaps you could wait to clear the image until the memory cache check completes?

It would be awesome if you have an idea for another solution here, otherwise I think this will lead to a slightly degraded UX for situations like the one described above. Thanks for the awesome library!