Hi all,
Is necessary and safe to switch to CoWaitForMultipleHandles?
Currently I try to verify the change like this, but I am not familiar with
the function, don't know how to choose the first parameter, I saw some code
using 0, which even not a legal value in API document.
DWORD hIndex;
HRESULT hret = CoWaitForMultipleHandles(1, INFINITE, 1,
&m_evtThreadReady, &hIndex);
Thanks
-Huai Dong
On Fri, Dec 4, 2009 at 2:00 AM, Huaidong Qiu <[email protected]> wrote:
> Maybe the DropTarget::initialize calling thread does not have a message
> loop, but DropTarget::initialize does create a COM object:
> m_pDropTarget= new IDropTargetImpl( *static_cast<DropTarget*>( this)
> );
> This means the calling thread needs a message loop.
>
> This freeze is hard to reproduce in our system, I think maybe because the
> COM calls into the COM object of the thread during the waiting period are
> very rare, but the freeze could happen.
