PSS ID Number: 221911Article Last Modified on 5/13/2003 -------------------------------------------------------------------------------- The information in this article applies to: Microsoft Visual C++, 32-bit Enterprise Edition 6.0, when used with: the operating system: Microsoft Windows NT Microsoft Windows 2000 Professional Microsoft Windows 2000 Server Microsoft Windows 2000 Advanced Server--------------------------------------------------------------------------------This article was previously published under Q221911 SYMPTOMS The Windows NT Task Manager shows an increase in memory usage every time the Visual C++ integrated debugger is started using F5 and then stopped. When the system exhausts the virtual memory limit, the application and debugger crashes displaying the following 3 message boxes: Microsoft Visual C++ "Could not execute: Path not found (win 32 error3)"Microsoft Visual C++ "DM0025: Error attaching to Process"Sample.exe- Application Error "The application failed to initialize properly (0xc000012d) Click on OK to terminate the application" RESOLUTION The memory can be freed before the system runs out of virtual memory by closing the Visual C++ IDE. STATUS Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Visual C++ .NET.MORE INFORMATION Steps to Reproduce Behavior Create a default MFC application using the AppWizard and build it. Start Windows NT Task Manager, click the Performance tab and watch MEM Usage. Start the integrated debugger by pressing F5. Note MEM Usage. Stop the debugger. Repeat steps 3-5. NOTE: Mem Usage has increased by quite some amount. If the virtual memory limit is reached then the errors messages described above are seen.
可以尝试更新GDI和SDK看看问题能不能解决
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Visual C++, 32-bit Enterprise Edition 6.0, when used with:
the operating system: Microsoft Windows NT
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server--------------------------------------------------------------------------------This article was previously published under Q221911
SYMPTOMS
The Windows NT Task Manager shows an increase in memory usage every time the Visual C++ integrated debugger is started using F5 and then stopped. When the system exhausts the virtual memory limit, the application and debugger crashes displaying the following 3 message boxes:
Microsoft Visual C++ "Could not execute: Path not found (win 32 error3)"Microsoft Visual C++ "DM0025: Error attaching to Process"Sample.exe- Application Error "The application failed to initialize properly (0xc000012d)
Click on OK to terminate the application"
RESOLUTION
The memory can be freed before the system runs out of virtual memory by closing the Visual C++ IDE.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Visual C++ .NET.MORE INFORMATION
Steps to Reproduce Behavior
Create a default MFC application using the AppWizard and build it.
Start Windows NT Task Manager, click the Performance tab and watch MEM Usage.
Start the integrated debugger by pressing F5.
Note MEM Usage.
Stop the debugger.
Repeat steps 3-5.
NOTE: Mem Usage has increased by quite some amount. If the virtual memory limit is reached then the errors messages described above are seen.