Memory Leak: MS-DOS-Based Apps Starting Non-MS-DOS-Based Apps

MS-DOS-based applications that start Windows-based, POSIX, or OS/2-based applications under Windows NT may experience memory leaks.

Two different memory leaks can occur. One memory leak occurs when the MS- DOS-based application does not close a Process Object handle properly.

To observe the memory leak:

1. Run Performance Monitor.
2. From the Edit menu, choose Add to Chart.
3. From the Object list box, select Objects.
4. From the Counter list box, select Processes.
5. Choose Add and then choose Done.

A leakage of this resource will result in the gradual depletion of non- paged pool (a vital Windows NT resource).



The other memory leak occurs when an MS-DOS-based application continuously starts non-MS-DOS-based applications, creating a looping situation. This results in the loss of Private Bytes associated with NTVDM.EXE running the MS-DOS-based application.

To observe the memory leak:

1. Run Performance Monitor.
2. From the Edit menu, choose Add to Chart.
3. From the Object list box, select Process.
4. From the Instances list box, select NTVDM.
5. From the Counter list box, select Private Bytes.
6. Choose Add and then choose Done.

It may be difficult to log if there are multiple instances of NTVDM running, as Performance Monitor will not let you distinguish between these instances if they share the same executable name. (The Windows NT Resource Kit describes methods to overcome this situation.) A leakage of this resource results in the gradual consumption of Private Bytes for the NTVDM.EXE process. Private bytes consumption is general backed by paging file so a leak of Private Bytes will slowly consume the pagefile (a vital Windows NT resource).

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 3.5. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):