Microsoft KB Archive/299007

= Triggering Events to an eMbedded Visual Basic Program Causes a Memory Leak =

Article ID: 299007

Article Last Modified on 4/7/2006

-

APPLIES TO


 * Microsoft Windows CE eMbedded Visual Basic-DO NOT USE! 3.0
 * Microsoft Windows CE Toolkit for Visual Basic 6.0

-



This article was previously published under Q299007



SYMPTOMS
Triggering events to an eMbedded Visual Basic program can cause a memory leak.



CAUSE
This issue occurs because a string is allocated for the event function name but is never released.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: eVB

Keywords: kbqfe kbenv kbprb kbhotfixserver KB299007

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.