Article ID: 813354 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
If you create an application by using the Microsoft .NET Framework version 1.0, and you use the DateTimePicker control in the application, you may notice a memory leak when you run the application.
This problem occurs because the garbage collector does not collect the inaccessible memory. The DateTimePicker control is associated with the Microsoft.Win32.UserPreferenceChangedEventHandler delegate. When you dispose of an object of the DateTimePicker control, this delegate is not dereferenced. Therefore, this delegate prevents the garbage collector from collecting the DateTimePicker control object.
To resolve this problem, obtain the latest service pack for the .NET Framework 1.0.
To obtain the latest service pack, visit the following Microsoft Web site:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in the Microsoft .NET Framework 1.0 Service Pack 3.
Steps to reproduce the behavior
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that Is used To describe Microsoft software updates
For more information about the UserPreferenceChangedEventHandler delegate, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/microsoft.win32.userpreferencechangedeventhandler(vs.71).aspxFor more information about the DateTimePicker class, visit the following MSDN Web site:
Contact us for more help
Connect with Answer Desk for expert help.