FIX: Memory Leak When Setting the ForeColor of a VB5 ObjectLast reviewed: December 18, 1997Article ID: Q171809 |
The information in this article applies to:
SYMPTOMSSetting the ForeColor property of an object (such as a form or a PictureBox) at design-time to a color other than a system defined color (a color that starts with &h8) causes memory leak in the GDI resources when the object is shown or hidden. This problem does not occur if the property is set during run-time.
RESOLUTIONThe workaround for this bug is to obtain Visual Studio 97 Service Pack 2 or leave/set the initial ForeColor property for the object to a system-defined color at design-time and set the desired ForeColor of the object at run- time. For example, the ForeColor property could be set to the desired color in the Form_Load event.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2. For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q170365 TITLE : INFO: Visual Studio 97 Service Packs - What, Where, and WhyFor a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q171554 TITLE : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2 Keywords : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2 Version : 5.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |