FIX: MSMQ AttachCurrentSecurityContext Calls May Leak Memory

Article translations Article translations
Article ID: 241751 - View products that this article applies to.
This article was previously published under Q241751
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

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.

RESOLUTION

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.

Properties

Article ID: 241751 - Last Review: February 21, 2014 - Revision: 3.1
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Message Queue Server 1.0
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbmsmq100fix KB241751

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com