Microsoft KB Archive/171809

From BetaArchive Wiki
Knowledge Base


FIX: Memory Leak When Setting the ForeColor of a Visual Basic 5.0 Object

Article ID: 171809

Article Last Modified on 2/16/2005



APPLIES TO

  • Microsoft Visual Basic 5.0 Control Creation Edition
  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition



This article was previously published under Q171809

SYMPTOMS

Setting 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.

RESOLUTION

The 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.

STATUS

Microsoft 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:

170365 : INFO: Visual Studio 97 Service Packs - What, Where, and Why



For 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:

171554 : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2


Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171809