Async is not cancelled

I have a function which load the image by click on button. If button is clicked twice (second click before async completion) it’s needed to cancel old async and start new. Code example:

private var deferred: Deferred<Bitmap>? = null
override fun onCreate(inState: Bundle?) {
        super.onCreate(inState)
        findViewById<View>(R.id.btn_action).setOnClickListener {
            if (deferred != null && deferred?.isActive == true) {
                Log.d("debug", "cancel")
                deferred?.cancel()
            }
            loadImage()
        }
    }

    private fun loadImage() = launch(UI) {
        Log.d("debug", "start")
        deferred = async {
           val conn = URL("http://elitefon.ru/pic/201503/2560x1600/elitefon.ru-38503.jpg").openConnection() as HttpURLConnection
            val bitmap = BitmapFactory.decodeStream(conn.inputStream)
            Log.d("debug", "end of async")
            return@async bitmap
        }
        deferred?.await()
        Log.d("debug", "loaded")
    }

In this case log will be something like this:

start
cancel
start
end of async
end of async
loaded

As we can see, in spite of cancel, “end of async” log is called twice. Also, try/catch logging shown that CancelationException is throws in the launch(UI) block (not the async block). Can I make it so that if I cancel async, the exception was thrown in the async block?

[SamKotlinFisher]

@fvasco, thanks for your answer. I developed the similar solution:

fun <T> async (block: () -> T): Deferred <T?> {
     var thread: Thread? = null
     val deferred = async (CachedPool) {
         thread = Thread.currentThread ()
         return @async block.invoke ()
     }
     deferred.invokeOnCompletion (true, true) {
         if (deferred.isCancelled && thread! = null && thread? .isAlive == true) {
             thread? .interrupt ()
             thread = null
         }
     }
     return deferred
}

What do you think about this?

[SamKotlinFisher]

@fvasco, thank you so much for your answer. I hope that this functionality will be able in kotlin-coroutine in a future as are described in #57.