You experience out of memory exception errors on a Web
server that has Microsoft ASP.NET 1.1 installed. ASP.NET 1.1 is installed as
part of the Microsoft .NET Framework 1.1 and the Microsoft .NET Framework 1.1
Service Pack 1 (SP1).
This problem occurs because the
MobileCapabilities object does not expire from the cache as expected. You can use an
instance of the
MobileCapabilities object to read the capabilities of the requesting browser and
device.
Hotfix information
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.1 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:
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
No prerequisites are required.
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
--------------------------------------------------------------
09-Dec-2004 01:15 1.1.4322.2045 258,048 Aspnet_isapi.dll
09-Dec-2004 01:15 1.1.4322.2045 32,768 Aspnet_wp.exe
09-Dec-2004 01:15 1.1.4322.2045 1,261,568 System.web.dll
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
A new
MobileCapabilities object is created and cached every time that a unique string in
the
<browserCaps> element is passed from the client browser in the User-Agent
header.
This hotfix modifies an attribute in the Machine.config file
that lets you configure the time that the
MobileCapabilities object remains in the cache before the
MobileCapabilities object expires. The following code example shows the default
setting in the
<browserCaps> element.
<result type="System.Web.Mobile.MobileCapabilities, System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
After you apply this hotfix, the
<result> element includes an attribute that lets you configure the time in
seconds before the
MobileCapabilities object expires. The following code example shows this attribute
set to the default value of 60 seconds.
<result cacheTime="60" type="System.Web.Mobile.MobileCapabilities, System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
For more information about the
MobileCapabilities class, visit the following Microsoft Developer Network (MSDN) Web
site:
For
more information, click the following article number to view the article in the
Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates