Hi Will, Can you make a minimal test case that shows the socket leakage? That's a first step to solving the problem.
> 2. There appears to be a bug with ZeroMQ's epoll implementation when a > socket gets into the EPOLLERR or EPOLLHUP state. ZeroMQ unregisteres the > socket for read, but doesn't actually call EPOLL_CTL_DEL on the fd, so epoll > just keeps calling back zmq with the same fd. Is this a know bug? I also > tried fixing this, but now it crashes in set_pollout periodically and > appears to be passing in a garbage fd, so I must have missed something. Again, if there's any way to reproduce this, that's a good start. Otherwise, file an issue and note as much about the problem as you can. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
