On 11/16/16 4:35 AM, unDEFER wrote:
On Tuesday, 15 November 2016 at 20:46:59 UTC, Steven Schveighoffer wrote:From experience, this smells like a race condition.And I have found the error! And you are right! It is really race condition. The problem was that I had not one receiveTimeout() but 3 receiveTimeout() for each thread. I don't know how I expect that each send must go to his own receiveTimeout, but of course it was false. Big thanks to all!
Glad you figured it out! -Steve