Article ID: 257650
Article Last Modified on 10/6/2005
APPLIES TO
- Microsoft Outlook 2000 Standard Edition
This article was previously published under Q257650
SYMPTOMS
Microsoft Visual Basic code that uses Collaboration Data Objects (CDO) and that logs on to a mailbox, gets a folder object, and then sets the object to nothing in a loop causes a memory leak.
CAUSE
The reference count for an internal object never reaches zero and it is reallocated, which causes the memory leak.
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. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service release that contains this hotfix.
To resolve this problem immediately, 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:
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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English-language version of this fix should have the following file attributes or later:
File Version Size Date ------------------------------------------------------- Emsmdb32.dll 5.05.3126.0000 590,096 3/16/00
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
Additional query words: OL2K
Keywords: kbbug kbfix kbqfe kbhotfixserver KB257650