<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Sorry: Windows 7.<br>
    <br>
    <div class="moz-cite-prefix">Em 18/11/2013 10:58, Felipe Farinon
      escreveu:<br>
    </div>
    <blockquote cite="mid:528A0EEE.1050803@powersyslab.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      Windows 8, ZeroMQ 3.2.2. I think that the problem is that the
      application is running in a test environment that doesn't close it
      graceously, instead it just terminates the application which
      leaves the possibility for that event to hang around. I have not
      tested with libzmq master, I have just fixed it myself using the
      mutex and the problem has gone away.<br>
      <br>
      Sure, I can submit the change mutex + port change myself.<br>
      <br>
      <div class="moz-cite-prefix">Em 13/11/2013 11:11, KIU Shueng Chuan
        escreveu:<br>
      </div>
      <blockquote
cite="mid:CAP2skc9jraMKJX0rKCqcU65v4egUrXV0R8pMq_dCg_-3erA56g@mail.gmail.com"
        type="cite">
        <p dir="ltr">Which versions of Windows and ZeroMQ does it happen
          on? Does your application open and close lots of ZeroMQ
          sockets? How about with libzmq master?</p>
        <p dir="ltr">Actually you could submit the change to mutex and
          port yourself?</p>
        <div class="gmail_quote">On Nov 13, 2013 3:02 AM, "Felipe
          Farinon" <<a moz-do-not-send="true"
            href="mailto:felipe.farinon@powersyslab.com">felipe.farinon@powersyslab.com</a>>

          wrote:<br type="attribution">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF"> My application is
              hanging frequently in one co-worker's machine. Whenever I
              diagnose the machine, I see the event still set with no
              application running. I'm afraid that when the application
              ships the bug happens much more.<br>
              <br>
              We wouldn't be taking "one more port", just changingthe
              old one.<br>
              <br>
              <div>Em 12/11/2013 10:52, KIU Shueng Chuan escreveu:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">I thought of the same thing before, port
                  5906 too. But I don't feel comfortable taking up one
                  more port without some consensus. Maybe if there were
                  more people reporting that their ZeroMQ applications
                  (with heavy socket creation!) were hanging on
                  Windows...
                  <div> <br>
                  </div>
                  <div>For now, I have modified signaler.cpp to not
                    assert within the "critical section".</div>
                  <div><a moz-do-not-send="true"
href="https://github.com/zeromq/libzmq/commit/4a7f07a19ae226fe92c3c7320bd425f9a18d0c79"
                      target="_blank">https://github.com/zeromq/libzmq/commit/4a7f07a19ae226fe92c3c7320bd425f9a18d0c79</a><br>
                  </div>
                </div>
                <div class="gmail_extra"><br>
                  <br>
                  <div class="gmail_quote">On Mon, Nov 11, 2013 at 11:16
                    PM, Felipe Farinon <span dir="ltr"><<a
                        moz-do-not-send="true"
                        href="mailto:felipe.farinon@powersyslab.com"
                        target="_blank">felipe.farinon@powersyslab.com</a>></span>
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <div text="#000000" bgcolor="#FFFFFF"> Maybe we
                        could change signaler_port to another value and
                        define that port 5905 is protected by the Event
                        and the new port (e.g. 5906) is protected by
                        Mutex. This way we don't need to check if the
                        Event is present.<br>
                        <br>
                        <div>Em 11/11/2013 11:16, Felipe Farinon
                          escreveu:<br>
                        </div>
                        <div>
                          <div>
                            <blockquote type="cite"> Ok.<br>
                              <br>
                              Seems reasonable to me and I think that a
                              4 seconds timeout is fine. The only
                              scenario where I could imagine that this
                              would break is if some heavy socket
                              creation is going on and IFF the
                              WaitForSingleObject wakeup order for
                              Events is not FIFO.<br>
                              <br>
                              <div>Em 11/11/2013 11:02, KIU Shueng Chuan
                                escreveu:<br>
                              </div>
                              <blockquote type="cite">
                                <p dir="ltr">Realistically, I think only
                                  bind, accept and connect have a chance
                                  of failing. The rest of the asserts
                                  just test for programming errors.
                                  Accept and connect are already
                                  handled. What's left is handling bind
                                  error.</p>
                                <br>
                                <fieldset></fieldset>
                                <br>
                                <pre>_______________________________________________
zeromq-dev mailing list
<a moz-do-not-send="true" href="mailto:zeromq-dev@lists.zeromq.org" target="_blank">zeromq-dev@lists.zeromq.org</a>
<a moz-do-not-send="true" href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev" target="_blank">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a>
</pre>
                              </blockquote>
                              <br>
                              <br>
                              <fieldset></fieldset>
                              <br>
                              <pre>_______________________________________________
zeromq-dev mailing list
<a moz-do-not-send="true" href="mailto:zeromq-dev@lists.zeromq.org" target="_blank">zeromq-dev@lists.zeromq.org</a>
<a moz-do-not-send="true" href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev" target="_blank">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a>
</pre>
                            </blockquote>
                            <br>
                          </div>
                        </div>
                      </div>
                      <br>
                      _______________________________________________<br>
                      zeromq-dev mailing list<br>
                      <a moz-do-not-send="true"
                        href="mailto:zeromq-dev@lists.zeromq.org"
                        target="_blank">zeromq-dev@lists.zeromq.org</a><br>
                      <a moz-do-not-send="true"
                        href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev"
                        target="_blank">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a><br>
                      <br>
                    </blockquote>
                  </div>
                  <br>
                </div>
                <br>
                <fieldset></fieldset>
                <br>
                <pre>_______________________________________________
zeromq-dev mailing list
<a moz-do-not-send="true" href="mailto:zeromq-dev@lists.zeromq.org" target="_blank">zeromq-dev@lists.zeromq.org</a>
<a moz-do-not-send="true" href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev" target="_blank">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a>
</pre>
              </blockquote>
              <br>
            </div>
            <br>
            _______________________________________________<br>
            zeromq-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:zeromq-dev@lists.zeromq.org">zeromq-dev@lists.zeromq.org</a><br>
            <a moz-do-not-send="true"
              href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev"
              target="_blank">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a><br>
            <br>
          </blockquote>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
zeromq-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:zeromq-dev@lists.zeromq.org">zeromq-dev@lists.zeromq.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
zeromq-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:zeromq-dev@lists.zeromq.org">zeromq-dev@lists.zeromq.org</a>
<a class="moz-txt-link-freetext" href="http://lists.zeromq.org/mailman/listinfo/zeromq-dev">http://lists.zeromq.org/mailman/listinfo/zeromq-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>