Open Hollaar opened 7 years ago
The problem is caused by the LogFile thread: Even if OSCWidgets is idle (no controls) it consumes all CPU cycles of one core.
By adding a short sleep the problem is solved.
Because the messages are buffered, the sleep can be as long as desired. I decided to sleep for 100ms.
I uploaded a commit with this fix:
commit d6aff6119175fe692d115d3c614ecd7ac8757c4a
I also created a pull request:
https://github.com/ETCLabs/OSCWidgets/pull/17
Hope this helps!
Just starting OSCWidgets with a five-button control window results in it using close to 50% of the CPU, as indicated by Process Explorer. Processor is an Intel Pentium G640 at 2.8 GHz, operating system is Windows 10 Home.