Microsoft KB Archive/241751

= FIX: MSMQ AttachCurrentSecurityContext Calls May Leak Memory =

Article ID: 241751

Article Last Modified on 7/16/2004

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Message Queue Server 1.0

-



This article was previously published under Q241751



SYMPTOMS
Microsoft Message Queue (MSMQ) applications that make more than one call to AttachCurrentSecurityContext will leak memory bytes on each subsequent call.



CAUSE
During the handling of the AttachCurrentSecurityContext, old security handles were not freed when the MSMQ runtime overrode an existing security handle. Each override acquired additional memory from private bytes resulting in a memory leak.



Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Calls to MQFreeSecurityContext were added in order to properly release private byte memory acquired when AttachCurrentSecurityContext was called.



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

This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Additional query words: msmq private bytes memory leak

Keywords: kbbug kbfix kbmsmq100fix KB241751

-

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

© Microsoft Corporation. All rights reserved.