FIX: Slow Performance When the Browser Capabilities Evaluator Is Removed from the Cache

This article has been archived. It is offered "as is" and will no longer be updated.
If available memory is low, the browser capabilities evaluator object may be removed from the cache. When the browser capabilities evaluator object is required again, it is re-created.

When a process generates many objects, the garbage collection process starts. The garbage collector removes the browser capabilities object evaluator from cache and the load/unload cycle repeats.

Note This problem occurs under high stress conditions.

How to Obtain the Hotfix

This issue is fixed in the June 2003 ASP.NET Hotfix Package 1.1. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
821156 INFO: ASP.NET 1.1 June 2003 Hotfix Rollup Package
You cannot obtain this fix individually. You must install the rollup.

Note When you request this hotfix, you receive the rollup.

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		   -----------------------------------------------------------------------		   07-Jun-2003  00:44  1.1.4322.910    253,952  Aspnet_isapi.dll		   07-Jun-2003  00:44  1.1.4322.910     20,480  Aspnet_regiis.exe		   07-Jun-2003  00:44  1.1.4322.910     32,768  Aspnet_wp.exe		   15-May-2003  23:49                   33,522  Installpersistsqlstate.sql		   15-May-2003  23:49                   34,150  Installsqlstate.sql		   07-Jun-2003  12:52  1.1.4322.910  1,216,512  System.dll		   07-Jun-2003  00:39                   14,472  Webuivalidation.js		   07-Jun-2003  12:52  1.1.4322.910  1,249,280  System.Web.dll

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Steps to Reproduce the Behavior

  1. Create a low memory condition. Verify that memory pressure is such that either of the following is true:
    • Memory Available MBytes is approximately 10 percent of PHYSICAL_RAM.

    • Private Bytes for the worker process is within 10 percent of the memory limit.
  2. When a request is made for a page under light stress, and the browser capabilities evaluator object has been removed from cache, performance is slow while this resource is being regenerated.
  3. In FileMon, note that the hard disk is in use repeatedly to gain access to the Machine.config file.

Article ID: 819612 - Last Review: 02/27/2014 21:18:47 - Revision: 4.2

  • Microsoft .NET Framework 1.1
  • Microsoft ASP.NET 1.1
  • kbnosurvey kbarchive kbbug kbfix kbqfe kbnetframe100presp3fix kbhotfixserver KB819612