Article ID: 909766
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft .NET Framework 1.1 Service Pack 1
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Visual Studio .NET 2003 Enterprise Architect
- Microsoft Visual Studio .NET 2003 Enterprise Developer
- Microsoft Visual Studio .NET 2003 Academic Edition
SYMPTOMS
In an application that was built by using Microsoft Visual Studio .NET 2003, you compile a large solution that contains more than 65 projects. When you do this, a memory leak may occur. Additionally, you may not be able to build the solution. When this problem occurs, Visual Studio .NET 2003 may unexpectedly close and then restart.
This problem occurs when one of the following conditions is true:
You compile source code that uses declarative security in C# code. For example, you compile source code that resembles the following code.
[SecurityPermission(SecurityAction.Demand,SerializationFormatter =false)] public void GetLeak() { }- You set the Allow unsafe code blocks property to True, and then you build an application that uses unsafe code.
RESOLUTION
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 Microsoft .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
To apply this hotfix, you must have the .NET Framework 1.1 Service Pack 1 (SP1) installed on the computer.
Restart requirement
You do not have to 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 item in Control Panel.
| File name | File version | File size | Date | Time | Platform | SP requirement |
|---|---|---|---|---|---|---|
| Corperfmonext.dll | 1.1.4322.2355 | 81,920 | 25-Oct-2005 | 22:57 | x86 | SP1 |
| Mscorlib.dll | 1.1.4322.2355 | 2,142,208 | 25-Oct-2005 | 22:21 | x86 | SP1 |
| Mscorsvr.dll | 1.1.4322.2355 | 2,523,136 | 25-Oct-2005 | 22:58 | x86 | SP1 |
| Mscorwks.dll | 1.1.4322.2355 | 2,510,848 | 25-Oct-2005 | 22:58 | x86 | SP1 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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 kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB909766
