XCLN: Memory Leak in Loop Accessing Collaboration Data Objects

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q252757

Expand all | Collapse all

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.

Back to the top

CAUSE

The reference count for an internal object never reaches zero and it is reallocated, which causes the memory leak.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

191014 (http://support.microsoft.com/kb/191014/EN-US/ ) XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Exchange Server 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Back to the top

MORE INFORMATION

The following code may cause the memory leak:

Dim CdoExpStore As InfoStore
Dim i As Integer
Dim Cdoexpfolder As MAPI.Folder

    For i = 1 To 10000
        Set Cdoexpfolder = CdoExpStore.RootFolder
        Set Cdoexpfolder = Nothing
    Next i

Back to the top

APPLIES TO

Microsoft Exchange Server 5.5 Standard Edition

Back to the top

kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbqfe KB252757

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top