Introduction

This article describes a hotfix that resolves the following issues.

Issue 1

When you are running a .NET Framework 2.0-based application, the application crashes. If you debug the application, you notice that a System.InsufficientMemoryException exception is thrown. Then, you receive an error message that resembles the following:

Issue 2

You run a .NET Framework 2.0-based application on a computer that has more than 8 logical processors. The computer uses the server garbage collector. In this case, you may experience a memory issue caused by an unbalanced workload in different processors. For example, the application runs slower than when you run the application on a computer that has 8 logical processors.

Cause of Issue 1

This issue occurs intermittently when the application tries to allocate memory for a large object in a large object heap (LOH). The error message is triggered when the following conditions are true:

• The heap cannot provide sufficient memory to satisfy the LOH allocation request.
• A concurrent garbage collection is in progress at the same time.

Cause of Issue 2

This issue occurs because garbage collector heap balancing for small object allocations is not performed diligently on computers that have more than 8 logical processors. Because of this, more garbage collections are triggered to maintain heap balancing when there is an unbalanced workload in different processors. Therefore, the application spends more time on garbage collection.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

To resolve this problem immediately, 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 website:Note 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.

Prerequisites

You must have the .NET Framework 2.0 Service Pack 2 or the .NET Framework 3.5 Service Pack 1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x86-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP

For all supported x64-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP

For all supported Itanium-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP

For all supported x86-based versions of Windows Vista SP2 and Windows Server 2008 SP2

For all supported x64-based versions of Windows Vista SP2 and Windows Server 2008 SP2

For all supported Itanium-based versions of Windows Server 2008 SP2

For all supported x86-based versions of Windows 7.0

For all supported x64-based versions of Windows 7.0 and Windows Server 2008 R2

For all supported Itanium-based versions of Windows Server 2008 R2

You notice the garbage collector operation when you troubleshoot an application by using a debugger. For more information about the garbage collector operation, see the following Microsoft website:

To work around Issue 1, disable the concurrent garbage collection for the common language runtime (CLR). To do this, you can reference the following Microsoft Web site:

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