CancellationException behavior in Kotlin - Time & Space Complexity

Time Complexity: CancellationException behavior

O(n)

Understanding Time Complexity

When working with Kotlin coroutines, it's important to understand how cancellation affects program flow.

We want to see how the CancellationException influences the running time of coroutine code.

Scenario Under Consideration

Analyze the time complexity of the following coroutine code snippet.

    suspend fun processItems(items: List<Int>) {
        for (item in items) {
            if (!kotlin.coroutines.coroutineContext.isActive) throw CancellationException()
            delay(10) // simulate work
            println(item)
        }
    }
    

This code processes a list of items, checking for cancellation before each step.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each item in the list.
• How many times: Once for each item in the input list.

How Execution Grows With Input

Each item causes a check for cancellation and a small delay, so work grows with the list size.

Input Size (n)	Approx. Operations
10	10 cancellation checks + 10 delays
100	100 cancellation checks + 100 delays
1000	1000 cancellation checks + 1000 delays

Pattern observation: The total work increases directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with the number of items processed.

Common Mistake

[X] Wrong: "CancellationException makes the loop stop immediately, so time is constant."

[OK] Correct: Cancellation only stops the loop when detected; until then, all items are processed, so time depends on input size.

Interview Connect

Understanding how cancellation affects coroutine loops helps you reason about program responsiveness and efficiency in real apps.

Self-Check

"What if the cancellation check was removed? How would the time complexity change?"

Practice

1. What is the primary purpose of CancellationException in Kotlin coroutines?

easy

A. To stop coroutines cleanly without treating it as an error

B. To indicate a syntax error in coroutine code

C. To force a coroutine to restart automatically

D. To log coroutine execution details

Solution

1. Step 1: Understand coroutine cancellation

   CancellationException is used to stop coroutines without throwing an error that crashes the program.

2. Step 2: Differentiate from errors

   Unlike other exceptions, CancellationException signals a normal cancellation, not a failure.

3. Final Answer:

   To stop coroutines cleanly without treating it as an error -> Option A

4. Quick Check:

   CancellationException stops coroutines cleanly [OK]

Hint: CancellationException means clean stop, not error [OK]

Common Mistakes:

• Confusing it with runtime errors
• Thinking it restarts coroutines
• Assuming it logs info automatically

2. Which of the following is the correct way to catch a CancellationException in Kotlin?

easy

A. catch (Error e) { /* handle */ }

B. catch (Exception e) { /* handle */ }

C. catch (Throwable e) { /* handle */ }

D. catch (CancellationException e) { /* handle */ }

Solution

1. Step 1: Identify exception type

   CancellationException is a specific exception type used for coroutine cancellation.

2. Step 2: Use specific catch block

   To handle cancellation properly, catch CancellationException explicitly.

3. Final Answer:

   catch (CancellationException e) { /* handle */ } -> Option D

4. Quick Check:

   Catch CancellationException explicitly [OK]

Hint: Catch CancellationException by its own type [OK]

Common Mistakes:

• Catching only Exception hides cancellation
• Using catch (Error) which is unrelated
• Catching Throwable catches too broadly

3. What will be the output of this Kotlin coroutine code snippet?

import kotlinx.coroutines.*

fun main() = runBlocking {
    val job = launch {
        try {
            repeat(3) { i ->
                println("Working $i...")
                delay(100)
            }
        } catch (e: CancellationException) {
            println("Cancelled!")
        } finally {
            println("Cleanup done.")
        }
    }
    delay(150)
    job.cancelAndJoin()
    println("Done")
}

medium

A. Working 0...
Working 1...
Cancelled!
Cleanup done.
Done

B. Working 0...
Working 1...
Working 2...
Done

C. Cancelled!
Cleanup done.
Done

D. Working 0...
Cancelled!
Done

Solution

1. Step 1: Trace coroutine execution and cancellation

   The coroutine prints "Working 0..." and "Working 1..." with 100ms delay each, then cancellation occurs after 150ms.

2. Step 2: Handle CancellationException and finally block

   CancellationException is caught, printing "Cancelled!" and finally block prints "Cleanup done." before main prints "Done".

3. Final Answer:

   Working 0... Working 1... Cancelled! Cleanup done. Done -> Option A

4. Quick Check:

   CancellationException caught, cleanup runs, then Done [OK]

Hint: CancellationException triggers catch and finally blocks [OK]

Common Mistakes:

• Ignoring finally block output
• Assuming all repeats run before cancel
• Missing cancellation catch output

4. Identify the problem in this Kotlin coroutine snippet that tries to handle cancellation:

val job = launch {
    try {
        delay(1000)
    } catch (e: Exception) {
        println("Cancelled")
    }
}
job.cancel()

medium

A. The coroutine never starts because launch is missing parentheses

B. Calling job.cancel() without join causes a deadlock

C. It catches Exception instead of CancellationException, so cancellation is not handled properly

D. delay(1000) cannot be cancelled

Solution

1. Step 1: Check exception handling

   The catch block catches Exception, which includes CancellationException but does not distinguish it from other exceptions.

2. Step 2: Understand cancellation propagation

   To specifically handle cancellation without catching unrelated exceptions, catch CancellationException explicitly.

3. Final Answer:

   It catches Exception instead of CancellationException, so cancellation is not handled properly -> Option C

4. Quick Check:

   Catch CancellationException explicitly to handle cancellation [OK]

Hint: Catch CancellationException, not just Exception [OK]

Common Mistakes:

• Assuming Exception catch handles cancellation
• Thinking delay is uncancellable
• Confusing cancel() with deadlock

5. You want to cancel a coroutine but still perform some cleanup code without treating cancellation as an error. Which pattern correctly uses CancellationException to achieve this?

hard

A. Avoid catching exceptions and rely on coroutine scope cancellation only

B. Use try-catch with catch (CancellationException) to handle cancellation and run cleanup in finally

C. Use a global exception handler to catch all exceptions including cancellation

D. Use try-catch with catch (Exception) and ignore finally block

Solution

1. Step 1: Understand cancellation handling best practice

   CancellationException should be caught explicitly to avoid treating cancellation as failure.

2. Step 2: Use finally block for cleanup

   Cleanup code belongs in finally to ensure it runs whether coroutine completes or is cancelled.

3. Final Answer:

   Use try-catch with catch (CancellationException) to handle cancellation and run cleanup in finally -> Option B

4. Quick Check:

   Catch CancellationException and cleanup in finally [OK]

Hint: Catch CancellationException and cleanup in finally block [OK]

Common Mistakes:

• Catching only Exception hides cancellation
• Skipping finally block for cleanup
• Relying on global handlers for cancellation