Difference between revisions of "Microsoft KB Archive/171503"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - "&" to "&")
 
(2 intermediate revisions by the same user not shown)
Line 22: Line 22:
 
== SYMPTOMS ==
 
== 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.
+
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.
  
 
<br />
 
<br />
Line 38: Line 38:
 
For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
 
For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
  
<blockquote>[[mk:@MSITStore:kbvstud.chm::/Source/vstudio/q170365|Q170365]] INFO: Visual Studio 97 Service Packs - What, Where, and Why</blockquote>
+
<blockquote>[[../170365|Q170365]] INFO: Visual Studio 97 Service Packs - What, Where, and Why</blockquote>
 
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:
 
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:
<blockquote>[[../vbwin/q171554|Q171554]] INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2</blockquote>
+
<blockquote>[[../171554|Q171554]] INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2</blockquote>
 
Additional query words:
 
Additional query words:
  

Latest revision as of 12:29, 21 July 2020

FIX: Memory Leak When Setting the ForeColor of VB5 Object

ID: Q171503



The information in this article applies to:

  • Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0




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 Basic 5.0 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:

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

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

Additional query words:

Keywords : kbVBp500 kbVS97sp2fix kbGrpVB kbvbp500sp2fix
Version : 5.0
Platform : WINDOWS
Issue type : kbbug


Last Reviewed: January 5, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.