BUG: Visual C++ Crashes when Exiting or Closing a Workspace

• Microsoft Visual C++, 32-bit Editions, versions 5.0, 6.0

SYMPTOMS

When quitting Visual C++ or when closing a workspace, you receive the following error message:

msdev.exe - Application Error
The instruction at "0x519eccb8" referenced memory at "0x0238ec99". The memory could not be read.
Click OK to terminate the application
Click CANCEL to debug the application

CAUSE

This error occurs when there are more than 4,086 source files in a workspace, regardless of the number of projects the workspace contains.

RESOLUTION

1. If your workspace contains more than one project, remove projects from the workspace until the source file sum is less than 4,086.



2. If your workspace consists of a single project, reduce the number of source file by removing the necessary number of files from the project or by merging files.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

When presented with the error message described in the Symptoms section of this article, you have two options:

• Clicking OK will simply dismiss the dialog box. You must then open Task Manager or PView to manually stop the Msdev.exe process.



• Clicking Cancel will start the Visual C++ debugger (if JIT debugging has been enabled). Once the process has been loaded, you will receive another error message:
  

  Microsoft Visual C++
  Unhandled exception in msdev.exe (DEVNCB.PKG): 0xC0000005: Access Violation.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q208155 PRB: BK1503 when Building Large .bsc File

Additional query words:

Keywords : kbide kbVC kbVC500bug kbVC600bug kbDSupport kbGrpDSTools
Version : winnt:5.0,6.0
Platform : winnt
Issue type : kbbug