Hey, we've implemented a multi threaded solution based on node via additional v8 and libuv. currently we are basing on node 10.11 -15 which is libuv 1.23 Now, we have a strange issue which keeps reappearing in different cases where a message sent by server to the client (libuv based client) isn't recieved. I've used wireshark to check and verified that the packets are recieved (and ack'd) but the "onread" cb of libuv isn't being called. I've checked the event loop and it seem to be stuck (?) on poll I/O. It always happens after almost the same set of operation which include running the eventloop (with UV_DEFAULT_RUN) -> pausing to run some JS code using v8 and back to running event loop (Again much much similar to Node.js).
Right, I haven't found a way to workaround this issue.. is there anyone that have seen this? found a workaround or a solution? Maybe some kind of proper tracing? I'm keen to understand why is the polling stuck as it should have very small timeout. Any clue is welcome. Thanks ahead, Fima. -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
