FIX: Multi-Use OLE .Exe File Not Releasing Memory

MORE INFORMATION

In a multi-use out-of-process OLE server, memory usage increases with each additional instantiation of an object or class in the server. When you release these class instantiations, memory usage does not decrease until the last object is released. Memory then decreases incrementally and the .exe file unloads from memory.

Steps to Reproduce Behavior

1. Create and build an out-of-process (.exe) multi-use OLE server in Microsoft Visual FoxPro.
   
   NOTE: To create a Multi-Use OLE server, click the Servers tab in the Project Information dialog box and select Multi Use for the Instance option.
2. In Microsoft Visual FoxPro create an instance of the OLE server.
3. Using a tool like Microsoft Windows NT Task Manager, view the memory usage for the OLE .exe file. In Microsoft Windows NT, this is located on the Processes tab of the Task Manager.
4. Create additional instances of the object and note the increased memory usage of the OLE .exe file.
5. Release instances of the object one by one and note that the memory usage does not decrease.
6. Release the last instance of the OLE server. Notice the memory decreases and the .exe file exits from the Processes list.