On Mon, Jun 25, 2012 at 01:04:30PM +0200, Christophe Fergeau wrote:
> It happens at more or less random times, so I'm not sure if I'll be able to
> catch a backtrace when the watch is removed.
Luckily watches don't get removed very often, so I managed to catch both
the remove and the following upd
On Mon, Jun 25, 2012 at 11:03:16AM +0100, Daniel P. Berrange wrote:
> On Wed, Jun 20, 2012 at 12:29:51PM +0200, Christophe Fergeau wrote:
> > The deletion of libvirt timeouts/watches is done in 2 steps:
> > - the first step is synchronous and unregisters the timeout/watch
> > from glib mainloop
>
On Wed, Jun 20, 2012 at 12:29:51PM +0200, Christophe Fergeau wrote:
> The deletion of libvirt timeouts/watches is done in 2 steps:
> - the first step is synchronous and unregisters the timeout/watch
> from glib mainloop
> - the second step is asynchronous and triggered from the first step.
> It
The deletion of libvirt timeouts/watches is done in 2 steps:
- the first step is synchronous and unregisters the timeout/watch
from glib mainloop
- the second step is asynchronous and triggered from the first step.
It releases the memory used for bookkeeping for the timeout/watch
being delete
