{"action":"created","issue":{"url":"https://api.github.com/repos/nanomsg/nanomsg/issues/554","labels_url":"https://api.github.com/repos/nanomsg/nanomsg/issues/554/labels{/name}","comments_url":"https://api.github.com/repos/nanomsg/nanomsg/issues/554/comments","events_url":"https://api.github.com/repos/nanomsg/nanomsg/issues/554/events","html_url":"https://github.com/nanomsg/nanomsg/issues/554","id":118642356,"number":554,"title":"weird hang/crash & race against nn_term","user":{"login":"gdamore","id":1295229,"avatar_url":"https://avatars.githubusercontent.com/u/1295229?v=3","gravatar_id":"","url":"https://api.github.com/users/gdamore","html_url":"https://github.com/gdamore","followers_url":"https://api.github.com/users/gdamore/followers","following_url":"https://api.github.com/users/gdamore/following{/other_user}","gists_url":"https://api.github.com/users/gdamore/gists{/gist_id}","starred_url":"https://api.github.com/users/gdamore/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gdamore/subscriptions","organizations_url":"https://api.github.com/users/gdamore/orgs","repos_url":"https://api.github.com/users/gdamore/repos","events_url":"https://api.github.com/users/gdamore/events{/privacy}","received_events_url":"https://api.github.com/users/gdamore/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":19,"created_at":"2015-11-24T16:07:02Z","updated_at":"2015-12-02T03:06:59Z","closed_at":null,"body":"I think there is a problem with the req/rep state machines racing with nn_term.\r\n\r\nhttps://ci.appveyor.com/project/gdamore/nanomsg/build/1.0.193/job/haswhuvgk3tv2lgr\r\n\r\nI can't explain this crash, or hang, any other way; something doesn't add quite up.  The problem is seriously complicated to debug, due to the gazillion state machines involved. \r\n\r\nInterestingly enough, increasing the timeout for the connection request, which allows the TCP connections to be established properly, seems to clear this problem up.  (Its also relevant that this problem only was seen on Windows, which seems to require quite a bit longer for TCP to establish.)"},"comment":{"url":"https://api.github.com/repos/nanomsg/nanomsg/issues/comments/161165710","html_url":"https://github.com/nanomsg/nanomsg/issues/554#issuecomment-161165710","issue_url":"https://api.github.com/repos/nanomsg/nanomsg/issues/554","id":161165710,"user":{"login":"wirebirdlabs","id":1944203,"avatar_url":"https://avatars.githubusercontent.com/u/1944203?v=3","gravatar_id":"","url":"https://api.github.com/users/wirebirdlabs","html_url":"https://github.com/wirebirdlabs","followers_url":"https://api.github.com/users/wirebirdlabs/followers","following_url":"https://api.github.com/users/wirebirdlabs/following{/other_user}","gists_url":"https://api.github.com/users/wirebirdlabs/gists{/gist_id}","starred_url":"https://api.github.com/users/wirebirdlabs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wirebirdlabs/subscriptions","organizations_url":"https://api.github.com/users/wirebirdlabs/orgs","repos_url":"https://api.github.com/users/wirebirdlabs/repos","events_url":"https://api.github.com/users/wirebirdlabs/events{/privacy}","received_events_url":"https://api.github.com/users/wirebirdlabs/received_events","type":"User","site_admin":false},"created_at":"2015-12-02T03:06:59Z","updated_at":"2015-12-02T03:06:59Z","body":"> I don't think these failures are only on Windows, but rather, only in single test environments.\r\n\r\nMissed a key word: \"only in **single core** test environments\""}}