BUG: Memory Leak in Visual C++ Integrated Debugger

ID: Q221911

The information in this article applies to:
  • Microsoft Visual C++, 32-bit Enterprise Edition, version 6.0
    on the following platforms: NT
  • Windows 2000

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 this to be a bug in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a default MFC application using the AppWizard and build it.


  2. Start Windows NT Task Manager, click the Performance tab and watch MEM Usage.


  3. Start the integrated debugger by pressing F5.


  4. Note MEM Usage.


  5. Stop the debugger.


  6. 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.


REFERENCES

(c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Vidyanand N. Rajpathak, Microsoft Corporation.

Additional query words:

Keywords : kbDebug kbide kbWinOS2000 kbVC600bug kbVS600
Version : WINDOWS:6.0; :
Platform : WINDOWS
Issue type : kbbug


Last Reviewed: January 17, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.