On Wed, Jul 13, 2016 at 12:36 PM, Ieio <[email protected]> wrote: > Many thanks Ben, > I will try to track each time I make a an uv_write and do not free anything > before the callback is called. > Should I pay attention not to call uv_close, before the uv_write callback > is called ? > > By the way I updated to the latest version of libuv.
It's safe to call uv_close() when there are still outstanding writes, they will be canceled. Their callbacks are invoked with status == UV_ECANCELED, don't free their memory before that. Similarly, don't free the handle's memory until the close callback. -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
