FIX: Performance slows in memory-intensive programs after you apply the hotfix that KB article 817618 describes

View products that this article applies to.

SYMPTOMS

On a multiprocessor computer, if you use the Mscorwks.dll file after you have applied the hotfix that Microsoft Knowledge Base article 817618 (http://support.microsoft.com/kb/817618/EN-US/ ) discusses, the performance of your memory-intensive programs slows down.

Back to the top

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 Microsoft .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 (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.

The English version of this hotfix has the file attributes (or later) 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
   --------------------------------------------------------------
   12-Aug-2003  09:17  1.0.3705.449    200,704  Aspnet_isapi.dll
   12-Aug-2003  09:11                    4,169  Aspnet_perf.h
   12-Aug-2003  09:18                  513,302  Aspnet_perf.ini
   12-Aug-2003  09:18                  510,714  Aspnet_perf2.ini
   12-Aug-2003  09:18  1.0.3705.449     24,576  Aspnet_regiis.exe
   12-Aug-2003  09:18  1.0.3705.449     28,672  Aspnet_wp.exe
   12-Aug-2003  08:40  1.0.3705.449     69,632  Corperfmonext.dll
   12-Aug-2003  08:38  1.0.3705.449    303,104  Mscorjit.dll
   12-Aug-2003  17:09  1.0.3705.449  1,953,792  Mscorlib.dll
   12-Aug-2003  08:31                   10,284  Mscorlib.ldo
   12-Aug-2003  08:39  1.0.3705.449  2,269,184  Mscorsvr.dll
   12-Aug-2003  08:39  1.0.3705.449  2,269,184  Mscorwks.dll
   01-Aug-2002  14:38                       15  Smartnav.htm
   29-Jul-2003  13:30                    8,728  Smartnav.js
   12-Aug-2003  17:07  1.0.3705.449  1,196,032  System.web.dll
   12-Aug-2003  17:07  1.0.3705.449     32,768  TlbImp.exe

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

If you run the PerfMon.exe file to view the .NET CLR Memory counter, you may notice that many generation 2 garbage collectors (also known as full garbage collectors) are working in the program. You may also notice that these garbage collectors use a lot of processing capacity (memory). Because there is less memory available for the processing requirements of your program, the performance of the program slows down.

Back to the top