[zeromq-dev] 0MQ multicast message lost?

ntupel at googlemail.com ntupel at googlemail.com
Fri Oct 8 15:29:04 CEST 2010

On Fri, Oct 8, 2010 at 3:02 PM, Steven McCoy <steven.mccoy at miru.hk> wrote:
> Missing timer, or rather failure trying to cancel a cancelled timer, not
> sure how this can occur.  File a bug on github, a stack trace would be
> pretty handy.

Will do so. In the meantime here is the stack trace:

#0  0x00002aaaabd45265 in raise () from /lib64/libc.so.6
#1  0x00002aaaabd46d10 in abort () from /lib64/libc.so.6
#2  0x00002aaaaacf6717 in zmq::poller_base_t::cancel_timer
(this=<value optimized out>, sink_=0x607b40, id_=161) at
#3  0x00002aaaaacf0d95 in zmq::pgm_receiver_t::in_event
(this=0x607b40) at pgm_receiver.cpp:139
#4  0x00002aaaaaceabca in zmq::epoll_t::loop (this=0x602190) at epoll.cpp:160
#5  0x00002aaaaacffbb7 in zmq::thread_t::thread_routine
(arg_=0x6021f8) at thread.cpp:79
#6  0x00002aaaab36d73d in start_thread () from /lib64/libpthread.so.0
#7  0x00002aaaabde8d1d in clone () from /lib64/libc.so.6

> Source is dropping NAKs as the sequences are outside of the transmit window.
>  Usual ways forward are increasing the transmit window size or decreasing
> the transmission rate.

I'll try.

Many thanks,

More information about the zeromq-dev mailing list