BUG: IWindows::Next and IDocuments::Next Leak Memory (266298)
The information in this article applies to:
- Microsoft Visual C++, 32-bit Enterprise Edition 5.0
- Microsoft Visual C++, 32-bit Enterprise Edition 6.0
- Microsoft Visual C++, 32-bit Professional Edition 5.0
- Microsoft Visual C++, 32-bit Professional Edition 6.0
- Microsoft Visual C++, 32-bit Learning Edition 6.0
This article was previously published under Q266298 SYMPTOMS
When you call the IWindows::Next or IDocuments::Next method to automate the Visual C++ Integrated Development Environment (IDE), you may see a memory leak. This leak is approximately 4 bytes for each time the IWindows::Next or IDocuments::Next method is called.
CAUSE
This problem is caused by a bug in the automation layer code for the Visual C++ IDE.
RESOLUTION
After prolonged use, the IDE may need to be closed and restarted because the leak may cause the system to become low on resources. If you restart the IDE, memory that was leaked is freed and the system regains the resources that were consumed.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
To reproduce this leak, compile the ReplAll Visual C++ add-in sample and run the sample in the Visual C++ IDE. You can find the ReplAll sample in the MSDN index by searching on ReplAll.
The leak is noticeable by using a memory monitoring tool such as Task Manager in Microsoft Windows NT. View the memory usage for the Msdev.exe file.
Modification Type: | Major | Last Reviewed: | 12/11/2003 |
---|
Keywords: | kbAutomation kbBug kbide kbnofix KB266298 |
---|
|