Re: [gtk-vnc-devel] [PATCH] Fix vnc_display_open followed by immediate vnc_display_close

[Anthony Liguori <anthony codemonkey ws>]

Richard W.M. Jones wrote:
> If you call one of the vnc_display_open* functions followed quickly by 
> vnc_display_close, then the library segfaults.
>
> The reason is that the vnc_display_open* functions register an idle 
> callback to launch the coroutine, but if vnc_display_close is called 
> before the idle loop has had a moment to run, this idle callback 
> remains.  The coroutine later runs - in my case, after the plugin I'm 
> writing has been unmapped from memory, with unhappy consequences.
>
> The attached patch fixes this by remembering the callback ID and 
> unregistering it if necessary.

Applied.  Thanks!

Regards,

Anthony Liguori

> Rich.
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gtk-vnc-devel mailing list
> Gtk-vnc-devel lists sourceforge net
> https://lists.sourceforge.net/lists/listinfo/gtk-vnc-devel