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. On Wednesday, July 13, 2016 at 12:01:43 PM UTC+2, Ben Noordhuis wrote: > > On Wed, Jul 13, 2016 at 9:30 AM, Ieio <[email protected] <javascript:>> > wrote: > > Hi all, > > I am developing a small application that acts as proxy. > > It worked fine for a couple of days, but today it sent a SIGABRT with > the > > following message: > > src/unix/stream.c:929: uv__write_callbacks: Assertion `(((const QUEUE > *) > > (&(stream->loop)->active_reqs) == (const QUEUE *) (*(QUEUE **) > > &((*(&(stream->loop)->active_reqs))[0]))) == 0)' failed. > > I gave a look into src/unix/stream.c, and for what I understood the > write > > queue is not empty, I haven't neither clue of what could have triggered > this > > situation nor of how to avoid it. > > Any suggestions? > > > > Thanks in advance, > > I. > > It probably means you have memory corruption in your application > somewhere, like freeing the memory of a uv_write_t or uv_tcp_t object > before libuv is done with it. > > Aside, the line number suggests that you are using a version of libuv > that is not the latest. Consider upgrading. > -- 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.
