Article ID: 884899 - Last Review: September 22, 2006 - Revision: 2.1

BUG: A memory leak may occur in an application that is built by using the .NET Framework 1.1 when the MessageQueue.Peek method throws an exception

Expand all | Collapse all

SYMPTOMS

When the following conditions are true, a memory leak may occur in an application that is built by using the Microsoft .NET Framework 1.1:
  • You use the MessageQueue.Peek method to return a message in the queue.

    Note The MessageQueue.Peek method returns the first message in the queue without removing the message from the queue.
  • The MessageQueue.Peek method throws an exception.
When this problem occurs, the memory usage for the application continues to increase. The garbage collection cannot free the memory that is used. Therefore, the memory usage reaches the limit of the virtual memory on the computer.

Additionally, an event that is similar to the following may be logged in the Application log:

Event Type: Error
Event Source: <program name>
Event Category: None
Event ID: 0
Date: <date>
Time: <time>
User: N/A
Computer: <server name>
Description:
Access to Message Queuing system is denied.
For more information, see Help and Support Center at http://support.microsoft.com

Note If the MessageQueue.Peek method does not throw an exception, the memory usage does not increase. Therefore, the memory leak does not occur.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft .NET Framework 1.1
Keywords: 
kbtshoot kbbug KB884899
 

Article Translations

 

Related Support Centers