FIX: MSMQ AttachCurrentSecurityContext Calls May Leak Memory

ID: Q241751

The information in this article applies to:

Microsoft Message Queue Server version 1.0

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

To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, please see the following article in the Microsoft Knowledge Base:

Q152734 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 this to be a problem in the Microsoft products listed at the beginning of this article.

This problem was first corrected in Windows NT 4.0 Service Pack 6.

Additional query words: msmq private bytes memory leak

Keywords : kbMSMQ kbMSMQ100 kbMSMQ100bug kbMSMQ100fix NT4SP6Fix
Version : winnt:1.0
Platform : winnt
Issue type : kbbug