You may be polling without any actual sleep. More precisely, you may
loop with a non blocking or "time-out equal to zero" polling, like a
"while(true) ;" which loads a cpu to 100%.
Le 18/06/2013 18:02, Pieter Hintjens a écrit :
On Tue, Jun 18, 2013 at 5:27 PM, Erwin Karbasi <[email protected]> wrote:
Any idea why the the machine has been overloaded to 100% CPU?
It could be a bug in libzmq, more likely you have a busy loop in your
application code. The way to diagnose the issue is to narrow down the
code to a minimal test case that we can reproduce. If it's an
application error you'll see it when you narrow down the test case,
and if not, we'll be able to reproduce and fix it.
Thanks
Pieter
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
