FIX: When you run a Microsoft ASP.NET-connected application that has custom URLs in the Microsoft .NET Framework 1.1, a memory leak occurs

View products that this article applies to.

SYMPTOMS

When you run a Microsoft ASP.NET-connected application that has custom URLs in the Microsoft .NET Framework 1.1, a memory leak occurs. This problem occurs only in the .NET Framework 1.1 Service Pack 1 (SP1).

Back to the top

CAUSE

ASP.NET caches assemblies to improve performance. When a user requests an .aspx file, the ASP.NET runtime searches for cached assemblies by using a key. This key was changed in the .NET Framework 1.1 Service Pack 1. Instead of using the physical path of the .aspx file, the key now uses the virtual path of the .aspx file. Because the virtual path is based on the URL, different custom URLs cannot use the same cached assemblies from the first URL request of an .aspx file. Instead, the assembly must be regenerated and then added to the cache. Therefore, the assembly cache grows with the number of unique virtual paths. This behavior eventually causes a very large assembly cache and high memory usage.

Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 (http://support.microsoft.com/kb/889100/ ) How to obtain the latest service pack for Windows Server 2003

Back to the top

Hotfix information

Prerequisites

There are no prerequisites.

Restart requirement

You must restart the computer after you apply this update.

Hotfix replacement information

This hotfix does not replace any other software updates.

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.

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Hashes
Aspnet_isapi.dll	1.1.4322.2359	258,048	13-Dec-2005	00:34	MD5: 6AF9D63D5422FB5A335D41C9C420743D SHA1: 4528173312B184DECD9F7362E8189D5238FF3F2E
Aspnet_wp.exe	1.1.4322.2359	32,768	13-Dec-2005	00:34	MD5: 925BC4045C49F521ED46FB832D9EDAFD SHA1: 269EBFB0423CC82644431AF93C3146F83E99F6C9
Netfxupdate.exe	1.0.3705.0	106,496	30-Aug-2005	00:02	MD5: 31FF1D32876C295C2F1C36ECF451F1D5 SHA1: 115964E21967B0F4727BEDD7E311E374ED21B3D4
Setregni.exe	1.1.4322.2034	106,496	30-Aug-2005	00:02	MD5: B692B9B743AB411F294C350F8DAE08C7 SHA1: 6C73A77CA8FF853FCF9E14ADFA68FF3B01BAF580
System.web.dll	1.1.4322.2359	1,265,664	12-Dec-2005	23:42	MD5: 38F61E2B39E0093E8413B235BB9BD952 SHA1: C62D52EFFFA1B7B12716FD27A7A482EE745FED76
Togac.exe	1.1.4322.573	118,784	18-Nov-2005	00:10	MD5: 60505C698E763DA37D45939DCD5C208A SHA1: CA3A4DE31A0211E8AFA377B7AFB75ECFC533CEFC

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. This problem was first corrected in Windows Server 2003 Service Pack 2.

Back to the top

MORE INFORMATION

How to implement this hotfix

This hotfix does not change the default behavior of the .NET Framework 1.1 SP1. The .NET Framework 1.1 SP1 still caches pages by using the virtual path. However, after you apply this hotfix, you can make a project configuration change to revert to the pre-.NET Framework 1.1 SP1 behavior of caching pages by using the physical path. To do this, create a Web.config file in the project folder, and then add the following code to the Web.config file.

Note If there is already a Web.config file in the project folder, only add the line that contains the <compilation> tag.

<?xml version="1.0"?>
<configuration>
<system.web>
  <compilation usePhysicalPathKey="true"/>
</system.web>
</configuration>

Note The default value for usePhysicalPathKey is false.

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

824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top