This article was previously published under Q257650
This article has been archived. It is offered "as is" and will no longer be updated.
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.
The reference count for an internal object never reaches zero and it is reallocated, which causes the memory leak.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.