Functions may leak memory if an exception is thrown by the COM object when you use #import to generate wrapper classes for COM objects (231872)

MORE INFORMATION

Steps to reproduce behavior

1. Create a Visual Basic COM server. You can choose ActiveX DLL.
2. Name the project LeakServer.
3. Name the class LeakTester.
4. Add one Public Sub called Leak to the class. For example:

          Public Sub Leak()
   
          End Sub
   					

5. Add the following code to the Leak Subroutine:

            Err.Raise vbObjectError + &H200 + 5
   					

6. Build the ActiveX DLL. When prompted, place the DLL on C drive.
7. Create a new MFC AppWizard-generated dialog box application. Name it LeakTest.
8. Add the following line to the Stdafx.h file:

        #import "C:\LeakServer.dll" no_namespace no_dual_interfaces
   					

9. Add a button and use Class Wizard to add a BN_CLICK handler.
10. Add the following code to the handler:

      _LeakTesterPtr serv;
      HRESULT hr = serv.CreateInstance(__uuidof(LeakTester));
      if (FAILED(hr))
      {
          TRACE("Create failed= %x\n", hr);
          return;
      }
    
      int nResponse = AfxMessageBox ("Catch 10 _com_errors?", MB_YESNO);
      while (IDYES == nResponse)
      {
         for (int iLoop = 0; iLoop < 10; iLoop++)
         {
            try
            {
              serv->Leak();
            }
            catch(_com_error &x)
            {
              int i = 0;
            }
        }
        nResponse = AfxMessageBox ("Catch 10 _com_errors?", MB_YESNO);
      }
    
    					

11. Add the following code before the button handler:

    struct InitCOM
    {
      InitCOM()  { CoInitialize(NULL); }
      ~InitCOM() { CoUninitialize();   }
    } g_Init;
    					

12. Build and test.