Hello! 27.05.2016, 18:04, "John Benediktsson" <[email protected]>: > Why do you have a busy loop on the callback? Why not just yield and return > out of it?
The busy loop is there to keep the new thread alive long enough so that I can see it in the Process Explorer. The 100% CPU utilization will 1) tell me that it's running, 2) help me tell it apart from the Listener's main thread hosted in the same process. > Maybe the callback is locking up the listener? The Listener doesn't lock up, it quits immediately. I have to start Factor.exe/com again. ---=====--- Александр ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
