Stefano Crespi

The issue is still present when using more than one core due to, I think, python's GIL. If you set the affinity to one or two cpu the bug is...

Yes, sure. Tried on three modern multicore PC with windows (2x win10 and 1x win11): If I paste the code on PCBASIC 2.0.6 without the A$=INKEY$ workaround: ``` 5 SCREEN...

I did some timing tests with and without A$=INKEY$ and using single or multi cpu affinity. [email protected] Windows 10 PC-BASIC 2.0.6 ``` 10 CLS:T=TIMER 20 FOR X= 1 TO 10000...

> I'm assuming you're running this on Python 3 - if it's the packaged Windows version it is Python 3. correct. I am not concerned about speed per se, what...

Further tests OS side (windows 10). It's interesting how different behave python 3 and python 2. I've used the same program [here](https://github.com/robhagemans/pcbasic/issues/166#issuecomment-1227331912) Single CPU affinity, with A$=INKEY$ (first half of...

You've fixed it! with your changes single and multi cpu speed are almost identical and the CPU load is back to normal. multi 24.39 sec  single 23.75 sec The...

@robhagemans do you have any eta of a new version that would include this fix?