Select the product you need help with

FIX: When you run a .NET Framework 2.0-based application, a System.AccessViolationException exception occurs, or a dead-lock occurs on two threads in an application domain

Article ID: 975954 - View products that this article applies to.

SYMPTOMS

You encounter one of the following problems when you run an application in the Microsoft .NET Framework 2.0.

Problem 1

Either a data corruption occurs or you receive a System.AccessViolationException exception. If you receive the exception, you also receive the following error message:

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

This problem occurs when all the following conditions are true:

An assembly is shared across multiple domains.
A Lightweight Code Gen (LCG) method is attached to a type that is inside the shared assembly.
The LCG method is collected in several domains. Then, the code in the assembly is compiled by a just-in-time (JIT) compiler.
Both the JIT code and the LCG method perform an interface call.

Problem 2

When you run the application on a computer that has high memory usage, the application stops responding. If you debug the problem by using the Windbg.exe tool, you find that a dead-lock occurs on two threads in an application domain.

Back to the top | Give Feedback

CAUSE

Cause of problem 1

The data corruption occurs because a common language runtime (CLR) stub function is no longer in committed memory after an application domain is recycled. The function was dynamically generated.

Cause of problem 2

The application stops responding because one thread obtains a lock to perform the m_prCachedMethodPermissionsLock function. Then, the thread is suspended to participate in garbage collection and does not release the lock. However, another thread that is in cooperative mode in the same application domain continues to wait for the lock.

Back to the top | Give Feedback

RESOLUTION

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. To download this hotfix from the Microsoft Developer Network (MSDN) Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB975954

(http://code.msdn.microsoft.com/KB975954)

Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

Alternatively, you can download this hotfix rollup from the following Microsoft Connect Web site:

https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=26146

(https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=26146)

Prerequisites

You must have the .NET Framework 2.0 Service Pack 2 (SP2) or the .NET Framework 3.5 Service Pack (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix if no instance of the .NET Framework is being used.

Hotfix replacement information

This hotfix does not replace 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 item in Control Panel.