FIX: MSMQ AttachCurrentSecurityContext Calls May Leak Memory

This article was previously published under Q241751
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Message Queue (MSMQ) applications that make more than one call to AttachCurrentSecurityContext will leak memory bytes on each subsequent call.
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 theMicrosoft 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.
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.
msmq private bytes memory leak

Article ID: 241751 - Last Review: 02/21/2014 00:38:16 - Revision: 3.1

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

  • kbnosurvey kbarchive kbbug kbfix kbmsmq100fix KB241751