FIX: Your .NET Framework 1.1 assembly may stop responding under low memory conditions after you run the Native Image Generator (Ngen.exe)

Article translations Article translations
Article ID: 839462 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you use the Native Image Generator (Ngen.exe) to create a native image from a managed assembly to help increase performance, your Microsoft .NET Framework 1.1 assembly may stop responding under low memory conditions.

CAUSE

This problem may occur when the application is run under low memory conditions and a deadlock condition occurs when garbage collection is performed.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for the .NET Framework 1.1. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
885055 How to obtain Microsoft .NET Framework 1.1 Service Pack 1

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:
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 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
   ---------------------------------------------------------------
   17-Apr-2004  03:32  1.1.4322.1031     77,824  Corperfmonext.dll  
   17-Apr-2004  03:29  1.1.4322.1031    282,624  Fusion.dll       
   17-Apr-2004  03:29  1.1.4322.1031    311,296  Mscorjit.dll     
   17-Apr-2004  03:32  1.1.4322.1031    102,400  Mscorld.dll      
   19-Apr-2004  07:23  1.1.4322.1031  2,093,056  Mscorlib.dll     
   17-Apr-2004  03:22                    10,756  Mscorlib.ldo
   17-Apr-2004  03:30  1.1.4322.1031  2,502,656  Mscorsvr.dll     
   17-Apr-2004  03:31  1.1.4322.1031  2,490,368  Mscorwks.dll     

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 the .NET Framework 1.1 Service Pack 1.

MORE INFORMATION

For additional 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

Properties

Article ID: 839462 - Last Review: April 7, 2006 - Revision: 2.1
APPLIES TO
  • Microsoft .NET Framework 1.1
Keywords: 
kbqfe kbhotfixserver kbnetframe110sp1fix kbfix kbbug KB839462

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com