FIX: You may experience frequent generation 2 garbage collection and high CPU usage by Aspnet_wp.exe on a computer that has the .NET Framework 1.0 SP2 installed (893222)


The information in this article applies to:

  • Microsoft Common Language Runtime (included with the .NET Framework) 1.0
For more information about how to resolve this problem on a computer that has the Microsoft .NET Framework 1.0 Service Pack 3 installed, click the following article number to view the article in the Microsoft Knowledge Base:

893058 FIX: You may experience frequent generation 2 garbage collection and high CPU usage by Aspnet_wp.exe on a computer that has the .NET Framework 1.0 Service Pack 3 installed

SYMPTOMS

You may experience frequent generation 2 garbage collection and high CPU usage by the Microsoft ASP.NET worker process (Aspnet_wp.exe). This problem occurs on a computer that has the Microsoft .NET Framework 1.0 Service Pack 2 (SP2) installed.

You may also notice that the ratio of garbage collections for each generation is much closer than expected.

CAUSE

This problem may occur when objects that are 85 kilobytes (KB) or larger are inserted into the large object heap. When objects that are 85 KB or larger are inserted into the large object heap, the common language runtime may not correctly manage the generation 2 heap and the large object heap.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 .NET Framework 1.0 service pack that contains this hotfix.

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

http://support.microsoft.com/contactus/?ws=support

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 Microsoft .NET Framework 1.0 SP2 installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any 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 tool in Control Panel. 
   Date         Time      Version       Size       File name
   ------------------------------------------------------------------------------------------------
   29-Jan-2005  02:04:22  1.0.3705.557    200,704  Aspnet_isapi.dll
   29-Jan-2005  01:49:34                    4,169  Aspnet_perf.h
   29-Jan-2005  02:04:36                  513,302  Aspnet_perf.ini
   29-Jan-2005  02:04:38                  510,714  Aspnet_perf2.ini
   29-Jan-2005  02:04:24  1.0.3705.557     24,576  Aspnet_regiis.exe
   29-Jan-2005  02:04:28  1.0.3705.557     28,672  Aspnet_wp.exe
   28-Jan-2005  23:09:38  1.0.3705.557     69,632  CORPerfMonExt.dll
   29-Apr-2003  14:59:46                   16,597  InstallPersistSqlState.sql
   29-Apr-2003  15:00:58                   17,331  InstallSqlState.sql
   12-Aug-2003  09:48:40                   17,807  InstallSqlStateTemplate.sql
   28-Jan-2005  23:04:18  1.0.3705.557    299,008  Mscorjit.dll
   30-Jan-2005  01:28:24  1.0.3705.557  1,953,792  Mscorlib.dll
   28-Jan-2005  22:50:40                   10,284  Mscorlib.ldo
   28-Jan-2005  23:05:22  1.0.3705.557  2,207,744  Mscorsvr.dll
   28-Jan-2005  23:06:26  1.0.3705.557  2,273,280  Mscorwks.dll
   29-Jan-2005  01:57:56  1.0.3705.557     20,480  PerfCounter.dll
   01-Aug-2002  13:38:14                       15  SmartNav.htm
   29-Jul-2003  12:30:08                    8,728  SmartNav.js
   30-Jan-2005  01:28:08  1.0.3705.557  1,179,648  System.Data.dll
   30-Jan-2005  01:28:24  1.0.3705.557  1,695,744  System.Design.dll
   30-Jan-2005  01:28:08  1.0.3705.557  1,175,552  System.dll
   30-Jan-2005  01:28:08  1.0.3705.557    241,664  System.Messaging.dll
   30-Jan-2005  01:28:08  1.0.3705.557    311,296  System.Runtime.Remoting.dll
   30-Jan-2005  01:28:06  1.0.3705.557    131,072  System.Runtime.Serialization.Formatters.Soap.dll
   30-Jan-2005  01:28:24  1.0.3705.557  1,200,128  System.Web.dll
   30-Jan-2005  01:28:08  1.0.3705.557    507,904  System.Web.Services.dll
   30-Jan-2005  01:28:24  1.0.3705.557  1,994,752  System.Windows.Forms.dll
   29-Jan-2005  02:18:08                   16,784  System.Windows.Forms.ldo
   29-Jan-2005  02:07:22  1.0.3705.557     57,344  System.Windows.Forms.tlb
   30-Jan-2005  01:28:24  1.0.3705.557  1,302,528  System.XML.dll
   30-Jan-2005  01:27:54  1.0.3705.557     32,768  TlbImp.exe
   08-Jan-2002  11:13:44                    1,419  UninstallPersistSqlState.sql
   12-Aug-2003  09:48:40                    2,119  UninstallSqlStateTemplate.sql
   30-Jan-2005  01:28:02  1.0.3705.557     65,536  Wsdl.exe

WORKAROUND

To work around this problem, use one of the following methods:
  • Minimize the size and the number of large objects that are used in the process.
  • Allocate large objects during the initial startup phase of the application.

STATUS

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

MORE INFORMATION

You can use Performance Monitor to view generation garbage collections. To view generation garbage collections, monitor the .NET CLR memory object and add the generation collection objects for Asp_wp.exe.

As a general guideline, there should be 10 generation 0 collections for each generation 1 collection. There should also be 10 generation 1 collections for each generation 2 collection.

This problem does not occur on computers that have the Microsoft .NET Framework 1.1 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

REFERENCES

For more information about garbage collection and memory management, visit the following Microsoft Web site:

http://msdn.microsoft.com/msdnmag/issues/1100/GCI

For more information about how to use garbage collection, visit the following Microsoft Web site:

http://blogs.msdn.com/maoni/archive/2004/06/15/156626.aspx

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbframe kbBug kbHotfixServer kbQFE kbpubtypekc KB893222 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.