Images are not shown reliably

Describe the bug If I inflate a layout, add it to a parent view and load an image into image view (one from my resources) I do so empty images every now and then.

E.g. I do create a menu dialog and for simplicity, I do add menu entries manually into a parent list view like following:

// following happens in a loop:
val b = DialogAppItemBinding.inflate(layoutInflater, binding.llRoot, true)
b.ivIcon.loadAny(item.icon) // this is a resource id

Expected behavior The image should always be loaded.

To Reproduce I can’t reproduce it reliably, it happens every now and then… Like in 1-2%

Logs/Screenshots

Version 1.1.1

My used image loader setup looks like following:

fun init(context: Context) {
      imageLoader = ImageLoader.Builder(context)
          .crossfade(false)
          .componentRegistry {
              // Fetchers
              add(AppIconFetcher(context))
              //add(AppIconFetcher2(context))
              // Decoders
              // ...
          }
          .okHttpClient {

              //val cacheDirectory = File(context.cacheDir, "image_cache").apply { mkdirs() }
              //val cacheSize = 250L * 1024 * 1024 // 250MB
              //val cache = Cache(cacheDirectory, cacheSize)

              OkHttpClient.Builder()
                  .cache(CoilUtils.createDefaultCache(context))
                  .build()
          }
          .apply {
              // Enable logging to the standard Android log if this is a debug build.
              if (BuildConfig.DEBUG) {
                  //logger(DebugLogger(Log.VERBOSE))
              }
          }
          // Workaround wegen issue: https://github.com/coil-kt/coil/issues/567
          .bitmapPoolingEnabled(false)
          //.launchInterceptorChainOnMainThread(false)
          .build()
      Coil.setImageLoader(imageLoader)
  }

[MFlisar]

I run my test project with 1.2.2 and it looks really good - I can’t reproduce the issue anymore in ~200 runs. Thanks

[colinrtwhite]

@MFlisar I just pushed 1.2.2 which includes a fix for a race condition that could cause this issue. Can you let me know if you’re still seeing the issue on the latest version?