A memory leak may occur when a Windows Forms-based application uses the MonthCalendar control, the DateTimePicker control, and the NumericUpDown control in a .NET Framework 1.1 application (893142)

The information in this article applies to:

Microsoft .NET Framework 1.1

SYMPTOMS

A memory leak may occur when a Microsoft Windows Forms-based application uses the following controls:

MonthCalendar
DateTimePicker
NumericUpDown

This problem occurs in the Microsoft .NET Framework 1.1.

CAUSE

This problem occurs because the MonthCalendar control, the DateTimePicker control, and the NumericUpDown control listen for system events. Therefore, these controls must be explicitly disposed before their parent forms are disposed. If you do not explicitly dispose these controls, a memory leak may occur.

RESOLUTION

To resolve this problem, you must explicitly dispose these controls by using the Dispose method. For example, to explicitly dispose the MonthCalendar control, you can use the MonthCalendar. Dispose method.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about these controls, visit the following Microsoft Developer Network (MSDN) Web sites:

MonthCalendar class
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwindowsformsmonthcalendarclasstopic.asp

DateTimePicker class
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwindowsformsdatetimepickerclasstopic.asp

NumericUpDown class
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwindowsformsnumericupdownclasstopic.asp

Modification Type:	Major	Last Reviewed:	4/27/2005
Keywords:	kbMemory kbProgramming kbControl kbWindowsForms kbtshoot kbprb kbbug KB893142 kbAudDeveloper kbAudITPRO