I think we’ve pretty much resolved most of the shutdown crashes. There are
still two main issues on the table for 1.0. The first is that there is
still a race condition around cleanups. Basically we can wind up
finalizing certain state machines and then have a thread submit content to
those state machines *after* the fact. I’ve got some ideas to resolve this
— and I feel there’s an excellent chance to fix this during the weekend.
The second issue is that I’d really like to fix the inproc MT safety
issues. I’ve researched this some more this week. I suspect we may be
able to fix that in the coming week.
The final issue, and one I’m on the fence about, is the idea to make
nn_bind() synchronous — at least the “listen and bind to address” part,
while the underlying accept() would be asynchronous. I have ideas as to
how to do this, but it involves some larger surgery, and it isn’t 100%
clear to me that we should hold back 1.0 pending this change, which IMO
would represent some risk.
On Fri, May 27, 2016 at 11:19 AM, Jay Berg <jaybny@xxxxxxxxx> wrote:
I heard the project is active again... this is great news! Where does
nanomsg stand regarding stability and the critical crash on shutdown
?especially on windows?
I'm a long time user of nanomsg and have lots of dormant code that uses
it. We are making a decision on a framework for a project, and we are
looking into 0MQ.. etc...
so, where do we stand? we also have resources that can help fix issues, if
this will bring the library stability and closer to production ready.. like