Apr 6, 2021

Dear Eric, From my testing, I can see that node.stop() is blocking. But, by reading node.stop()’s code i’m not quite clear what part of it actually blocks. Just for being really clear, I wish to ask you to confirm: node.stop() is blocking, right? Over on my side I am in GUI logic code that must not block, so I will then mitigate node.stop()’s blockingness, by spawning a separate OS thread wherein I will do node.stop(), and my GUI logics will nonblockingly wait/poll for that thread’s completion, thereby then knowing that node.stop() and node.close() completed. In my main thread, I would be fine with a sub-1-millisecond block by node.stop() and node.close(), but not more, in which case I like to spawn the separate OS thread as I suggest here. Any cue on what’s the appropriate action please let me know.