A memory leak occurs in a .NET Framework 2.0-based application that uses the AesCryptoServiceProvider class

Reason 1

Two native handles that are in a parent/child relationship in an AesCryptoServiceProvider object belong to separate managed objects. When the parent handle is disposed of first, the system cannot trace and then release all the memory that is owned by the child handle.

Reason 2

The AesCryptoServiceProvider object leaks a reference to an object in its ICryptoTransform interface.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft website:

http://code.msdn.microsoft.com/KB981575Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

You can also download this hotfix from the following Microsoft website:

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31185