I have verified that all my COM interfaces are released well. I think the apartment model causes the problem. I assume this as a result of the following observation: 1. There are two threads terminated when I close my App used with NetMeeting 3.0. 2. There is only one thread terminated when I close my App used with NetMeeting 2.1. Because my App doesn't open a second thread, the conf.exe of NetMeeting must be responsible for the second thread. How can I change the apartment model? The runtime-dlls are multithreaded. Defining _ATL_FREE_THREADED instead of _ATL_APARTMENT_THREADED before including <atlbase.h> in stdafx.h doesn't change anything. What can I do? How can I change the apartment modell? Werner -----Urspr�ngliche Nachricht----- Von: Rey Jean-Francois [SMTP:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 15. Juli 1999 08:35 An: [EMAIL PROTECTED] Betreff: Re: [NetMeeting] NM3SDK: WindowsApp remains in the process table Hi, if the process stays alive, I would think that it means that one of your com interface is not released well. If this happens when you're making / receiving a call then the interface involved must be used when placing your call. It could be also a thread problem. If you use single thread appartment, maybe you're calling one of the interfaces with another thread (it could explain the rpcrt4 error stuff). Regards. Werner Wendler wrote: > > I have a problem with closing my WindowsApplication. (snip) -- Jean-Francois Rey. ------------------- ALCATEL R&D Adv. Projects. ZI de Kergonan 29601 Brest FRANCE. phone : +33 (0) 298143322 fax : +33 (0) 298143501
