[vbox-dev] CMachine.SetExtraData() deadlocks
huisinro at yahoo.com
Tue Sep 20 15:56:59 PDT 2011
It's before the call, when deadlock occured, I attached the debugger, and then found out it's the windows WaitForObject call keeps waiting. Not sure if the server side finished the call or not. I will pay more attention next time.
--- On Tue, 9/20/11, Klaus Espenlaub <klaus.espenlaub at oracle.com> wrote:
From: Klaus Espenlaub <klaus.espenlaub at oracle.com>
Subject: Re: [vbox-dev] CMachine.SetExtraData() deadlocks
To: vbox-dev at virtualbox.org
Date: Tuesday, September 20, 2011, 2:27 PM
On 20.09.2011 18:40, Huihong Luo wrote:
> very rarely, I got deadlock by invoking this method.
> After debugging, it deads lock at WaitForSingleObject Windows API inside
> some rpc stub.
Is the deadlock before (or after) actually invoking the method? Haven't seen such issues in a long time, but if they're happening they're very nasty to debug, because the COM machinery internals is totally undocumented closed source code.
> What is the correct context to invoke this call? such as threading
VBoxSVC is a "local" COM service which by design supports arbitrary concurrency.
The caller should initialize the COM client side appropriately, but that's a generic requirement which isn't specific to VirtualBox.
> vbox-dev mailing list
> vbox-dev at virtualbox.org
vbox-dev mailing list
vbox-dev at virtualbox.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev