dotnet clr: Events: Do they lead to memory leaks? -- dotnet clr

You're in the

dotnet clr

group:

Events: Do they lead to memory leaks?

Re: Events: Do they lead to memory leaks?

David Browne
7/25/2003 9:16:21 AM

dotnet clr:

[quoted text, click to view]

Yes

[quoted text, click to view]

It will not be garbage collected.

David

Events: Do they lead to memory leaks?

Rahul Kumar
7/25/2003 10:09:31 AM

Hi all

I have the following scenario in brief: There are two classes EventRaiser
and EventConsumer. The EventRaiser raises an event and EventConsumer listens
to it, by adding its handler to the event chain of the EventRaiser's event
delegate. My question is: If the EventConsumer goes out of context, without
removing itself from the event chain, does the EventRaiser still have its
reference through the event chain? Will it not be garbage collected?

Regards

RK

Re: Events: Do they lead to memory leaks?

David Browne
7/25/2003 11:35:23 AM

[quoted text, click to view]

Well that's not how events are implemented, but they could have been.

If you used interfaces instead of events, you could use weak references to
notitify the object without keeping it from being collected.

But only good programming prevents this. You might make your objects
Disposable, and remove the event handler in the Dispose method.

David

Re: Events: Do they lead to memory leaks?

Rahul Kumar
7/25/2003 4:58:45 PM

Hi David

Thanks for the response. I have got few more questions for you:

How to take care of the memory leaks in such cases?
Are there in safeguards in .Net against it, except good programming
practices?
How about using WeakReferences to link the two Event objects?

Regards

Rahul

"David Browne" <davidbaxterbrowne no potted meat@hotmail.com> wrote in
message news:ekpBUdrUDHA.2192@TK2MSFTNGP09.phx.gbl...
[quoted text, click to view]

Re: Events: Do they lead to memory leaks?

Niall
7/28/2003 10:38:39 AM

Weak references could have worked in this situation. Bear in mind that it's
only really an issue when your object is hooking onto an event in another
object which has a significantly longer life span. But it can be a really
nasty situation, especially if it's not you hooking up the event, but
something in the framework, and your object ends up being referenced through
a static hashtable or similar.

Niall

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet clr group.

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn