FIX: You may notice a memory leak when you use the DateTimePicker control in the .NET Framework 1.0 (813354)
The information in this article applies to:
- Microsoft .NET Framework 1.0
SYMPTOMSIf 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. CAUSEThis 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.RESOLUTIONTo 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: STATUSMicrosoft 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.REFERENCESFor more information about the UserPreferenceChangedEventHandler delegate, visit the following Microsoft Developer Network (MSDN) Web site: For more information about the DateTimePicker class, visit the following MSDN Web site:
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbMemory kbGarbageCollect kbForms kbcode kbBug kbfix kbQFE kbNetFrame100preSP3fix KB813354 kbAudDeveloper |
---|
|