New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zloop gets confused if you create timer with same arg as expired timer #114
Comments
Test case: /*
|
If this was fixed in 95381bf shouldn't this be closed? |
@shancat, welcome to the CZMQ maintainers' group :-) Feel welcome to merge pull requests, close issues, and invite others to the group. This is our process: http://rfc.zeromq.org/spec:22 |
Wow thanks! Just happy to help :) I'll be sure to read that document |
Problem: if a timer expires (either by default, or by calling zloop_timer_end(), and you add a new timer with the same argument, zloop will destroy the new timer at the same time as it destroys the expired one.
Solution: when reaping zombie timers, only reap the first one. Secondly, add new timers to end of timer list, not start.
The text was updated successfully, but these errors were encountered: