Backtrace for the thread that has asserted:
https://gist.github.com/710510
I am hopeful the backtrace will be sufficient. There are a lot of sockets at work in a very complex system, so reducing it to a simple case is unlikely.
The assertion raises in my program when it is 1) under load, and 2) I hit ctrl-C or send a INT or TERM signal to end the program.
This is against commit ac40680ea2f6b32a3c of master.
I can no longer reproduce this. Closing.
Github Username: hexa00
I can reproduce this every time with a pub/sub scenario :
I'm using 2.1.3 using c++ bindings
Doing a publisher while (1) and a two part message (first part 10 bytes second 512 bytes) ...
And a subscriber while (1).. with a subscription to all channels..
2 threads are created... they stop after 10 secs ...
It seems to happen at the end.. maybe something to do with termination..
But the 2 threads are joined correctly and their sockets closed on destruction...
Then the context is destroyed...
Maybe a good idea to reopen ? I will try to make a simple app reproducing the issue..
Any ideas meanwhile are welcome...