`setTimeout()` doesn't fire unless the Qt event loop is active

[sedwards2009]

I just noticed that setTimeout() doesn't fire unless there is activity on the Qt event loop.

This sounds very similar to the problem reported here: nodegui/nodegui#864

[sedwards2009]

I am using the 16.4.1 version.

[sedwards2009]

Also, so far I've only noticed this problem on Windows.

[sedwards2009]

I also noticed that qode/NodeGui can get into a state where my app (a terminal) becomes very slow and sluggish. I strongly suspect this has to do with I/O events not being processed in a timely way.

I've spent some time debugging into this, and have found a couple interesting things so far which may be enough to explain the problem:

• Sometimes PostMessage() from the monitoring thread to the main thread (actually window) can fail. When this happens, the queue on the window is completely full and "over quota".
• The semaphore being used to coordinate the monitor thread and running the nodejs event processing on the main thread, gets hits by sem_post() many many times if you are doing I/O before the Qt event loop is entered. This causes the counter in the semaphore to be huge instead of 0 or 1. This gives the monitor thread the ability to spam PostMessage() in a tight loop

I've got some ideas which may fix these problems and my general problem, even if I don't quite figure out the exact details of how the symptoms appear.

[sedwards2009]

I'm pretty sure this is fixed now.