Event unsubscription and memory in C Sharp (C#) - Time & Space Complexity

Time Complexity: Event unsubscription and memory

O(n)

Understanding Time Complexity

When working with events in C#, it's important to understand how unsubscribing affects program performance and memory.

We want to see how the time to unsubscribe grows as more event handlers are attached.

Scenario Under Consideration

Analyze the time complexity of unsubscribing event handlers from an event.

public class Publisher
{
    public event EventHandler? OnChange;

    public void UnsubscribeAll()
    {
        if (OnChange == null) return;
        foreach (Delegate d in OnChange.GetInvocationList())
        {
            OnChange -= (EventHandler)d;
        }
    }
}
    

This code removes all handlers subscribed to the OnChange event one by one.

Identify Repeating Operations

Look for loops or repeated actions in the code.

• Primary operation: Looping through each subscribed event handler.
• How many times: Once for each handler attached to the event.

How Execution Grows With Input

The time to unsubscribe grows as the number of handlers increases.

Input Size (n)	Approx. Operations
10	About 10 loop steps to remove handlers
100	About 100 loop steps to remove handlers
1000	About 1000 loop steps to remove handlers

Pattern observation: The work grows directly with the number of handlers.

Final Time Complexity

Time Complexity: O(n)

This means the time to unsubscribe all handlers grows linearly with how many handlers there are.

Common Mistake

[X] Wrong: "Unsubscribing from an event is always a constant time operation."

[OK] Correct: Because unsubscribing here loops through all handlers, so more handlers mean more time needed.

Interview Connect

Understanding how event unsubscription scales helps you write efficient and memory-safe C# programs, a useful skill in many coding situations.

Self-Check

What if we stored handlers in a different data structure that allowed direct removal? How would the time complexity change?

Practice

1. What happens if you do not unsubscribe from an event in C#?

easy

A. The event will automatically unsubscribe after the first call.

B. The program will throw a compile-time error.

C. The subscriber object may not be garbage collected, causing a memory leak.

D. The event handler will be called only once.

Solution

1. Step 1: Understand event subscription behavior

   When an object subscribes to an event, the event publisher holds a reference to the subscriber's method.

2. Step 2: Effect of not unsubscribing

   If you don't unsubscribe, the subscriber object remains referenced and cannot be garbage collected, causing a memory leak.

3. Final Answer:

   The subscriber object may not be garbage collected, causing a memory leak. -> Option C

4. Quick Check:

   Not unsubscribing = memory leak [OK]

Hint: Always unsubscribe to avoid memory leaks and keep memory clean [OK]

Common Mistakes:

• Assuming events auto-unsubscribe
• Thinking unsubscribing causes errors
• Believing event handlers run only once

2. Which syntax correctly unsubscribes a method named OnDataReceived from an event DataReceived?

easy

A. DataReceived -= OnDataReceived;

B. DataReceived += OnDataReceived;

C. DataReceived = null;

D. DataReceived.Unsubscribe(OnDataReceived);

Solution

1. Step 1: Recall event unsubscription syntax

   In C#, to unsubscribe from an event, use the '-=' operator with the same method.

2. Step 2: Match correct syntax

   DataReceived -= OnDataReceived; uses 'DataReceived -= OnDataReceived;', which is the correct way to unsubscribe.

3. Final Answer:

   DataReceived -= OnDataReceived; -> Option A

4. Quick Check:

   Unsubscribe syntax = '-=' operator [OK]

Hint: Use '-=' with the same method to unsubscribe events [OK]

Common Mistakes:

• Using '+=' instead of '-=' to unsubscribe
• Trying to assign null to the event
• Using non-existent Unsubscribe method

3. What will be the output of the following code?

using System;
class Program {
  static event Action MyEvent;
  static void Handler() => Console.WriteLine("Called");
  static void Main() {
    MyEvent += Handler;
    MyEvent -= Handler;
    MyEvent?.Invoke();
  }
}

medium

A. Called

B. No output

C. NullReferenceException

D. Compile-time error

Solution

1. Step 1: Analyze event subscription and unsubscription

   The method Handler is subscribed then immediately unsubscribed from MyEvent.

2. Step 2: Check event invocation

   Since no handlers remain, MyEvent is null, so MyEvent?.Invoke() does nothing and prints no output.

3. Final Answer:

   No output -> Option B

4. Quick Check:

   Unsubscribed event = no call [OK]

Hint: Unsubscribed event handlers do not run when invoked [OK]

Common Mistakes:

• Expecting output despite unsubscription
• Ignoring null conditional operator
• Thinking event throws exception if empty

4. Identify the problem in this code snippet related to event unsubscription:

class Publisher {
  public event Action OnChange;
  public void Raise() => OnChange?.Invoke();
}
class Subscriber {
  public void Subscribe(Publisher p) {
    p.OnChange += HandleChange;
  }
  void HandleChange() {
    Console.WriteLine("Changed");
  }
}

medium

A. Subscriber never unsubscribes, causing potential memory leaks.

B. Event is invoked incorrectly with null conditional operator.

C. Handler method signature does not match event delegate.

D. Publisher event is not declared as static.

Solution

1. Step 1: Review subscription and unsubscription

   The Subscriber subscribes to the event but never unsubscribes.

2. Step 2: Understand consequences

   Without unsubscription, the Subscriber object remains referenced by Publisher, causing memory leaks.

3. Final Answer:

   Subscriber never unsubscribes, causing potential memory leaks. -> Option A

4. Quick Check:

   Missing unsubscribe = memory leak risk [OK]

Hint: Always unsubscribe to avoid memory leaks in event handlers [OK]

Common Mistakes:

• Ignoring unsubscription importance
• Confusing static and instance events
• Assuming null conditional operator causes errors

5. You have a long-running application where multiple subscribers attach to a static event but never unsubscribe. What is the best approach to prevent memory leaks?

hard

A. Replace events with polling loops to avoid subscription issues.

B. Make the event instance-level instead of static to avoid leaks.

C. Ignore unsubscription because garbage collector handles it automatically.

D. Use weak event patterns or explicitly unsubscribe when subscribers are no longer needed.

Solution

1. Step 1: Understand static event references

   Static events hold references for the app lifetime, so subscribers never get garbage collected unless unsubscribed.

2. Step 2: Best practice to avoid leaks

   Using weak event patterns or explicitly unsubscribing prevents memory leaks by releasing subscriber references.

3. Final Answer:

   Use weak event patterns or explicitly unsubscribe when subscribers are no longer needed. -> Option D

4. Quick Check:

   Weak events or unsubscribe = prevent leaks [OK]

Hint: Use weak events or unsubscribe explicitly to avoid leaks [OK]

Common Mistakes:

• Assuming GC cleans static event subscribers
• Changing event to instance-level without reason
• Replacing events with inefficient polling