Comments for .NET and Memory

Comment on Minor memory leak introduced in .NET Framework 2.0 SP1 by Richard

Richard — Fri, 12 Feb 2010 12:50:00 +0000

Thanks for the pointer - solved an issue for me today.

Comment on Memory Leak in ToolStripTextBoxControl by Arunprasad

Arunprasad — Thu, 23 Jul 2009 16:43:49 +0000

We are noticing memory leaks in the Web Forms version of the Microsoft ReportViewer control. However, we don’t have the Web Forms equivalent of the DisposeHelper class that you have implemented here.

Any suggestion / help would be great..

Comment on Memory Leak in ToolStripTextBoxControl by Keith

Keith — Fri, 01 May 2009 17:33:03 +0000

Microsoft reports this as being fixed on Microsoft Connect (#305199). The problem report was closed 2009/02/03 (it was reported on 2007/10/17).

Comment on Memory Leak in ToolStripTextBoxControl by Form not disposing due to lingering reference | keyongtech

Form not disposing due to lingering reference | keyongtech — Sun, 18 Jan 2009 17:20:59 +0000

[...] event handlers. The article I found describes how to do this using ToolStripTextBox as an example http://www.scitech.se/blog/index.php…extboxcontrol/ Following the steps described in the article I discovered, that my problem is caused by a [...]

Comment on Memory Leak in ToolStripTextBoxControl by Daniel

Daniel — Tue, 18 Nov 2008 15:59:39 +0000

Hi, tody I run in the same Problem with the datagridview.

But instead of unregistering all events like in the workaround, I just Dispose the datagridviews event list with a call to dispose like that.

mDataGridView.Events.Dispose();

This works well!

Comment on Memory Leak in ToolStripTextBoxControl by Oliver

Oliver — Wed, 20 Aug 2008 19:13:34 +0000

You dont need to do this somewhere?

m_textBox.VisibleChanged -= new EventHandler( textBox_VisibleChanged );
m_textBox.Disposed -= new EventHandler( textBox_Disposed );

Note the ” -= ”
Thanks

Comment on Memory Leak in ToolStripTextBoxControl by Roy

Roy — Mon, 23 Jun 2008 03:57:17 +0000

Probs something similar to

RemoveHandler SystemEvents.UserPreferenceChanged, AddressOf eventHandler

Comment on Memory Leak in ToolStripTextBoxControl by Andy smith

Andy smith — Mon, 31 Mar 2008 09:24:41 +0000

This article was very useful, i’m finding that i’m having the same problem with a DataGridView and want to apply the same logic to remove the rogue Event Handlers.

The only problem I’m having is we code in VB.Net and I cannot find the equivalent for the SystemEvents.UserPreferenceChanged -= eventHandler;
line.

Can you help.

Comment on Minor memory leak introduced in .NET Framework 2.0 SP1 by Asher

Asher — Thu, 20 Mar 2008 16:54:41 +0000

Very nice…
don’t you just love regression!

Comment on Memory Leak in ToolStripTextBoxControl by andreas

andreas — Sun, 10 Feb 2008 20:56:57 +0000

Everything in a root path is part of keeping an instance alive. To allow the instance to be GCed, the root path must be broken somewhere (all root paths needs to be broken). The reason for pointing out the UserPreferencesChangedEventHandler is that event handlers are very often involved when investigating a memory leak. If the event owner (producer) has a longer life-time than the listener, the event listener must be explicitly removed.

In this case, the bottom of the root path was the static field SystemEvents._handlers and a few entries up I found the event handler. Looking at the documentation reveals that the UserPreferencesChangedEventHandler is used by the static event UserPreferencesChanged. A static event lives for the whole duration of the process, so to avoid a memory leak the listener (the ToolStripTextBox) needs to removed from the event.