Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

C# How to unsubscribe all event handlers from a given event?

Is there a simple way to iterate all over the handlers subscribed to a given event? My problem is that clients subscribe but forget to unsubscribe so a memory leak happens. I need a way for an object to disconnect all the handlers of its events in the Dispose method so a leak would not happen - at least not because of events.

like image 668
Adi Barda Avatar asked Mar 28 '10 13:03

Adi Barda


People also ask

What C is used for?

C programming language is a machine-independent programming language that is mainly used to create many types of applications and operating systems such as Windows, and other complicated programs such as the Oracle database, Git, Python interpreter, and games and is considered a programming foundation in the process of ...

Is C language easy?

Compared to other languages—like Java, PHP, or C#—C is a relatively simple language to learn for anyone just starting to learn computer programming because of its limited number of keywords.

What is C in C language?

What is C? C is a general-purpose programming language created by Dennis Ritchie at the Bell Laboratories in 1972. It is a very popular language, despite being old. C is strongly associated with UNIX, as it was developed to write the UNIX operating system.

What is the full name of C?

In the real sense it has no meaning or full form. It was developed by Dennis Ritchie and Ken Thompson at AT&T bell Lab. First, they used to call it as B language then later they made some improvement into it and renamed it as C and its superscript as C++ which was invented by Dr.


2 Answers

Set null to your event: MyEvent = null;

But it is really better to make clients unsubscribing from your event.

like image 161
Andrew Bezzub Avatar answered Sep 18 '22 13:09

Andrew Bezzub


An alternative approach is to use so-called "weak delegate" pattern. When you use this technique, the event references clients only using WeakReference which doesn't keep them in memory. The clients will be garbage collected when they are no longer referenced from other part of the application (and the handler can be also unregistered automatically when the client is collected).

This is usually used to solve the problem with clients "forgetting" to unsubscribe from a .NET event, so it sounds like this might be well suited for your problem.

  • Dusing Campbell has a nice article about weak delegates.
  • I also liked this overview at CodeProject, which discusses most of the scenarios.
  • Weak Events are also used in WPF, but this approach seems a bit complicated (to me).
like image 33
Tomas Petricek Avatar answered Sep 18 '22 13:09

Tomas Petricek