You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.
OK, this has happened to me twice, now. The first time I restarted the PC and it started working again, so it feels like some kind of resource problem where ZMQ has used up all its resources and Windows can't allocate any more, so ZMQ just hangs.
I'm using Windows 7, Node 7.0.0, and ZMQ Node.js bindings 2.15.3.
Basically, things work fine for a while. I am stopping and starting my JS program quite often, and each time it's creating a new ZMQ socket. After a while though (maybe 100 starts of the program? that's just a guess), it starts hanging when I try to create a socket with zmq.socket('sockName'). I debugged it and traced the exact point at which my Node program hangs as index.js line 174:
ctx = new zmq.Context(io_threads);
(io_threads is 1.) Not sure why it hangs here. Why might it? Is there any further debugging I can do to see just what is causing it to hang?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
OK, this has happened to me twice, now. The first time I restarted the PC and it started working again, so it feels like some kind of resource problem where ZMQ has used up all its resources and Windows can't allocate any more, so ZMQ just hangs.
I'm using Windows 7, Node 7.0.0, and ZMQ Node.js bindings 2.15.3.
Basically, things work fine for a while. I am stopping and starting my JS program quite often, and each time it's creating a new ZMQ socket. After a while though (maybe 100 starts of the program? that's just a guess), it starts hanging when I try to create a socket with
zmq.socket('sockName')
. I debugged it and traced the exact point at which my Node program hangs as index.js line 174:(io_threads is 1.) Not sure why it hangs here. Why might it? Is there any further debugging I can do to see just what is causing it to hang?
The text was updated successfully, but these errors were encountered: