Microsoft KB Archive/911309

= 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 =

Article ID: 911309

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft .NET Framework 1.1 Service Pack 1

-





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).



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.



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 How to obtain the latest service pack for Windows Server 2003

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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Windows Server 2003 Service Pack 2.



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   tag.     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 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbwinserv2003sp2fix kbnetframe110presp2fix kbpubtypekc kbbug kbfix kbqfe kbhotfixserver KB911309

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.